Hello Ben,
I am here with a regression in the current 3.6 tree.
I just tried the latest tree from Linus (g26d29d0) and while nouveau
does find my card and its two connected displays, the ouput is somewhat
garbled: the colors are way wrong. For instance, the text console is a
pale green i
On Thu, Nov 22, 2012 at 10:20 PM, Grant Likely
wrote:
> On Thu, Nov 22, 2012 at 7:17 PM, Kay Sievers wrote:
>> On Wed, Nov 21, 2012 at 3:52 PM, Greg Kroah-Hartman
>> wrote:
>>> If the devices don't show up under platform/ where are they going to be
>>> at now, virtual/ ? That doesn't sound li
On Thu, Nov 22, 2012 at 01:31:07PM +0100, Lothar Waßmann wrote:
> also set MODULE_AUTHOR and MODULE_DESCRIPTION
Applied, thanks. But as ever please do write better changelogs, for
example "Add MODULE_ information" or something as the subject.
signature.asc
Description: Digital signature
On Thu, Nov 22, 2012 at 01:31:08PM +0100, Lothar Waßmann wrote:
> set the 'onwer' field of the registered snd_soc_card object to prevent
> removal of the module when its resources are in use.
Applied, thanks.
signature.asc
Description: Digital signature
On Fri, Nov 23, 2012 at 08:21:22AM +0100, Lothar Waßmann wrote:
> > On Thu, Nov 22, 2012 at 01:31:09PM +0100, Lothar Waßmann wrote:
> > Why?
> I thought that was obvious... To be able to compile the mxs sound
> driver as module.
Do you want to add new users of these functions, or are there exist
On 11/23/2012 12:34 AM, Minchan Kim wrote:
> On Thu, Nov 22, 2012 at 12:13:24PM +0100, Jerome Marchand wrote:
>> On 11/21/2012 09:37 AM, Minchan Kim wrote:
>>> Hi alls,
>>>
>>> Today, I saw below complain of lockdep.
>>> As a matter of fact, I knew it long time ago but forgot that.
>>> The reason l
On Tue, Nov 20, 2012 at 10:56:21AM +0100, Peter Ujfalusi wrote:
> The driver supports the following PWM outputs:
> TWL4030 PWM0 and PWM1
> TWL6030 PWM1 and PWM2
>
> On TWL4030 the PWM signals are muxed. Upon requesting the PWM the driver
> will select the correct mux so the PWM can be used. When t
>If you could instrument mem_cgroup_handle_oom with some printks (before
>we take the memcg_oom_lock, before we schedule and into
>mem_cgroup_out_of_memory)
If you send me patch i can do it. I'm, unfortunately, not able to code it.
>> It, luckily, happend again so i have more info.
>>
>> - t
On Tue, Nov 20, 2012 at 10:56:22AM +0100, Peter Ujfalusi wrote:
> The driver supports the following LED outputs as generic PWM driver:
> TWL4030 LEDA and LEDB (PWMA and PWMB)
> TWL6030 Charging indicator LED (PWM LED)
>
> On TWL6030 when the PWM requested LED is configured to be controlled by SW.
On Tue, Nov 20, 2012 at 10:56:20AM +0100, Peter Ujfalusi wrote:
> This driver only supported the Charging indicator LED.
> New set of drivers going to provide support for both PWMs and LEDs for twl4030
> and twl6030 series of PMICs.
>
> Signed-off-by: Peter Ujfalusi
> ---
> drivers/pwm/Kconfig
From: Alessandro Rubini
The header is used by drivers/dma/amba-pl08x.c, which can be compiled
under x86, where PL080 exists under a PCI-to-AMBA bridge. This patche
moves it where it can be accessed by other architectures, and fixes
all users.
Signed-off-by: Alessandro Rubini
Acked-by: Giancarlo
From: Alessandro Rubini
The sta2x11 I/O Hub is a bridge from PCIe to AMBA. It reuses a number
of amba drivers and needs to activate core bus support.
Signed-off-by: Alessandro Rubini
Acked-by: Giancarlo Asnaghi
---
arch/x86/Kconfig |4
1 file changed, 4 insertions(+)
diff --git a/ar
From: Alessandro Rubini
Signed-off-by: Alessandro Rubini
Acked-by: Giancarlo Asnaghi
---
drivers/mmc/host/mmci.c |2 +-
drivers/mmc/host/msm_sdcc.c |2 +-
drivers/mmc/host/mvsdio.c |2 +-
drivers/mmc/host/mxcmmc.c |2 +-
drivers/mmc/host/pxamci.c |3 +--
5 files c
From: Alessandro Rubini
This driver would not compile if ARM_AMBA is selected under x86,
because "CS" and "DS" are already defined there. But AMBA
is used in the x86 world by a PCI-to-AMBA bridge, to be submitted.
The patch adds the "PL330_" prefix to all register and bit fields,
so it can be b
From: Alessandro Rubini
The SP805 driver is only used by the Spear machines, and uses
writel_relaxed, which is not available on all architectures.
The dependency from CONFIG_ARM avoids compilation problems under
randomconfig when CONFIG_ARM_AMBA is enabled for x86 builds.
Signed-off-by: Alessan
From: Alessandro Rubini
This is a PCI driver that registers AMBA devices for the range of
supported devices. It is currently used by STA2X11, which exports
AMBA peripherals under PCIe. The original AMBA drivers work with no
changes or minimal ones.
Signed-off-by: Alessandro Rubini
Acked-by: G
Not all the architectures have readsl/writesl,
use the more portable ioread32_rep/iowrite32_rep functions instead.
Signed-off-by: Davide Ciminaghi
---
drivers/mmc/host/mmci.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/mmc/host/mmci.c b/drivers/mmc/host
From: Alessandro Rubini
Commit dece904d (gpio: pl061: use chained_irq_* functions in irq
handler) introduced chained_irq_enter/exit, which is only
available for arch/arm and the driver won't compile elsewhere.
The dependency is thus made explicit, because AMBA is used in the x86
world by a PCI-t
Hi,
this is v2 of a patchset submitted on Sep 14th
(see https://lkml.org/lkml/2012/9/14/412).
The only changes are:
* Rebased to next-20121115.
* "gpio: pl061 depends on ARM" : changelog fixed as per Sergei Shtylyov's
comments (see https://lkml.org/lkml/2012/9/14/471).
* "drivers/amba: add supp
Add support for reading conversion results from the ADC and provide them
through a single IIO channel. A proper scaling factor is also exported
based on the reference voltage provided by a regulator.
Signed-off-by: Thierry Reding
---
Changes in v2:
- use the more common IIO_VAL_FRACTIONAL_LOG2 in
This commit adds an RTC driver for PCF8523 chips by NXP Semiconductors.
No support is currently provided for the alarm and interrupt functions.
Only the time and date functionality is implemented.
Signed-off-by: Thierry Reding
---
Hi Andrew,
I'm resending this to you since I just read somewhere
The STMPE GPIO driver can be used as an IRQ controller by some
related devices. Here we provide it with its very own IRQ Domain
so that IRQs can be issued dynamically. This will stand the
driver in good stead when it is enabled for Device Tree, as this
it a prerequisite.
Cc: Grant Likely
Reviewed
Historically, a driver would have to decide whether it required
a Linear or Legacy IRQ domain when registering one. This can end
up as quite a lot of code. A new Simple call now exists which
simplifies this process. Let's make use of it here.
Cc: Samuel Ortiz
Reviewed-by: Viresh Kumar
Signed-off
Thorsten Leemhuis wrote on 20.11.2012 18:43:
> On 20.11.2012 16:38, Josh Boyer wrote:
>
> The short story from my current point of view is:
Quick update, in case anybody is interested:
> * my main machine at home where I initially saw the issue that started
> this thread seems to be running fin
On Fri, Nov 23, 2012 at 9:31 PM, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
>> * Alex Shi wrote:
>>
>> > >
>> > > Those of you who would like to test all the latest patches are
>> > > welcome to pick up latest bits at tip:master:
>> > >
>> > >git://git.kernel.org/pub/scm/linux/kernel/git/
On Fri, 2012-11-23 at 15:42 +0100, Helmut Jarausch wrote:
> with 3.7_rc6 and
>
> CONFIG_ACPI_VIDEO=m
> CONFIG_DRM=y
> CONFIG_DRM_KMS_HELPER=y
> CONFIG_DRM_TTM=y
> CONFIG_DRM_NOUVEAU=y
> CONFIG_NOUVEAU_DEBUG=5
> CONFIG_NOUVEAU_DEBUG_DEFAULT=3
> CONFIG_DRM_NOUVEAU_BACKLIGHT=y
>
> with/ without
> CO
Hi Guys,
Last week, I received two new interesting devices report:
- N-trig win 8 certified pen/touch panel
- Samsung Nexio 42"
N-trig device
-
The first one is the origin of patches 1 to 6.
The multiouch part worked flawlessly with the win 8 patches I sent before,
but the pen part w
On Friday 23 of November 2012 13:33:12 Thomas Abraham wrote:
> This patch series includes two minor updates to the gpio dvs code in
> max8997 regulator driver and adds device tree support for the same
> driver.
>
> Thomas Abraham (3):
> regulator: max8997: reorder buck1/2/5 dvs setup code
> re
This device is the worst device I saw. It keeps TipSwitch and InRange
at 1 for fingers that are not touching the panel.
The solution is to rely on the field ContactCount, which is accurate
as the correct information are packed at the begining of the frame.
Unfortunately, CountactCount is most of t
On Fri, 23 Nov 2012, Viresh Kumar wrote:
> On 23 November 2012 15:06, Lee Jones wrote:
> > On Fri, 23 Nov 2012, Viresh Kumar wrote:
> >> pdev = platform_device_alloc(cell->name, id + cell->id);
> >>
> >> This is required when we have multiple instances of MFD device present
> >> on board. H
On Fri, 23 Nov 2012, Viresh Kumar wrote:
> On 23 November 2012 17:44, Lee Jones wrote:
> > I'm saying, just leave it where it is.
>
> So you are suggesting this code:
>
> stmpe_gpio->chip.base = pdata ? pdata->gpio_base : -1;
>
>if (pdata)
>stmpe_gpio->norequest
On 23 November 2012 21:13, Lee Jones wrote:
> No, in DT devices named as part of the hiearchy, so you'd have:
>
> soc-u9500/i2c@80004000/stmpe1601@40/stmpe_keypad
> soc-u9500/i2c@80004000/stmpe1601@41/stmpe_keypad
> ... etc
Obviously. How could i miss this naming :(
Okay, so i need to pass -1 an
This driver can be built as a module, add MODULE_ALIAS for it.
Signed-off-by: Axel Lin
---
drivers/regulator/tps65090-regulator.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/tps65090-regulator.c
b/drivers/regulator/tps65090-regulator.c
index 3974a99..41c3917 100644
> Currently the BU21013 Touch Screen driver requests a regulator by the
> name of 'V-TOUCH', which doesn't exist anywhere in the kernel. The
> correct name, as referenced in platform regulator code is 'avdd'. Here,
> when we request a regulator, we use the correct name instead.
>
> Cc: Dmitry Toro
On Fri, Nov 23, 2012 at 8:38 PM, Davide Ciminaghi wrote:
> From: Alessandro Rubini
>
> This driver would not compile if ARM_AMBA is selected under x86,
> because "CS" and "DS" are already defined there. But AMBA
> is used in the x86 world by a PCI-to-AMBA bridge, to be submitted.
>
> The patch a
On Thu, 22 Nov 2012, Lee Jones wrote:
> Author: Lee Jones
> Date: Fri Sep 28 10:29:07 2012 +0100
>
> Input: bu21013_ts - Move GPIO init and exit functions into the driver
>
> These GPIO init and exit functions have no place in platform data.
> Instead they should be part of th
On Wed, 14 Nov 2012, Lee Jones wrote:
> Now we can register the BU21013_ts touch screen when booting with
> Device Tree enabled. Here we parse all the necessary components
> previously expected to be passed from platform data.
>
> Cc: Dmitry Torokhov
> Cc: linux-in...@vger.kernel.org
> Acked-by:
On Fri, Nov 23, 2012 at 8:38 PM, Davide Ciminaghi wrote:
> From: Alessandro Rubini
>
> The header is used by drivers/dma/amba-pl08x.c, which can be compiled
> under x86, where PL080 exists under a PCI-to-AMBA bridge. This patche
> moves it where it can be accessed by other architectures, and fixe
On Wed, 14 Nov 2012, Lee Jones wrote:
> This patch allows the STMPE driver to be successfully probed and
> initialised when Device Tree support is enabled. Besides the usual
> platform data changes, we also separate the process of filling in
> the 'in use' pin bitmap, as we have to extract the inf
On 1 November 2012 15:20, Ulf Hansson wrote:
> From: Ulf Hansson
>
> Due to the convert to the common clk driver these changes for clks are needed.
>
> Ulf Hansson (2):
> Input: nomadik-ske-keypad - fixup use of clk
> Input: nomadik-ske-keypad - start using the apb_pclk
>
> drivers/input/key
On Wed, 14 Nov 2012, Lee Jones wrote:
> Here we add the required documentation for the STMPE Device
> Tree bindings. It describes all of the bindings currently
> supported by the driver.
>
> Cc: Dmitry Torokhov
> Cc: linux-in...@vger.kernel.org
> Acked-by: Arnd Bergmann
> Acked-by: Linus Wallei
On Fri, Nov 23, 2012 at 8:38 PM, Davide Ciminaghi wrote:
> From: Alessandro Rubini
>
> The SP805 driver is only used by the Spear machines, and uses
> writel_relaxed, which is not available on all architectures.
>
> The dependency from CONFIG_ARM avoids compilation problems under
> randomconfig w
On Fri, Nov 23, 2012 at 8:38 PM, Davide Ciminaghi wrote:
> From: Alessandro Rubini
>
> Commit dece904d (gpio: pl061: use chained_irq_* functions in irq
> handler) introduced chained_irq_enter/exit, which is only
> available for arch/arm and the driver won't compile elsewhere.
>
> The dependency i
On Fri, Nov 23, 2012 at 8:38 PM, Davide Ciminaghi wrote:
> From: Alessandro Rubini
>
> Signed-off-by: Alessandro Rubini
> Acked-by: Giancarlo Asnaghi
Reviewed-by: Viresh Kumar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger
On 23 November 2012 14:49, Nicolas Ferre wrote:
> Add information to the DMA Configuration Register to
> maximize system performance:
> - rx/tx packet buffer full memory size
> - allow possibility to use INCR16 if supported
>
> Signed-off-by: Nicolas Ferre
Acked-by: Joachim Eastwood http://vger.
Hi Nicolas,
On 23 November 2012 14:50, Nicolas Ferre wrote:
> From: Havard Skinnemoen
>
> Allocate regular pages to use as backing for the RX ring and use the
> DMA API to sync the caches. This should give a bit better performance
> since it allows the CPU to do burst transfers from memory. It i
From: Vipul Kumar Samar
This patch allows the STMPE GPIO driver to be successfully probed and
initialised when Device Tree support is enabled. Bindings are mentioned in
Documentation too.
Signed-off-by: Vipul Kumar Samar
Signed-off-by: Viresh Kumar
---
V1->Resend:
--
- Don't move asign
On 23/11/12 15:53, James Hogan wrote:
> On 09/11/12 14:25, Arnd Bergmann wrote:
>> On Wednesday 31 October 2012, James Hogan wrote:
>>> +static inline void
>>> +dma_unmap_single(struct device *dev, dma_addr_t dma_addr, size_t size,
>>> +enum dma_data_direction direction)
>>> +{
>>>
15c3597d (dt/platform: allow device name to be overridden) added a
lookup parameter to of_platform_populate() but did not update the
documentation. This patch adds the missing documentation entry.
Cc: Grant Likely
Cc: Jiri Kosina
Signed-off-by: Javi Merino
---
drivers/of/platform.c |1 +
At least some older gcc versions dislike mixing constant and non-const
data in the same section ("... causes a section type confict"). Newer
gcc simply emits the section as writable (which isn't what we want, but
also is not a big problem as it gets discarded post-init anyway).
Also get the Knight
These items are only ever referenced from initialization code.
Signed-off-by: Jan Beulich
---
arch/x86/platform/efi/efi-bgrt.c |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
--- 3.7-rc6/arch/x86/platform/efi/efi-bgrt.c
+++ 3.7-rc6-x86-BGRT-init/arch/x86/platform/efi/efi-bgrt.c
Hi,
I had missed one pull request in the batch you merged yesterday. Better
keep them small and frequent at this point, so here it is.
The following changes since commit 5a903166dd31a42e39283b075cc6b9a9c079d1af:
Merge tag 'fixes-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/
The first two are functions serving as initcalls; the SFI one is only
being called from __init code.
Signed-off-by: Jan Beulich
---
arch/x86/kernel/cpu/intel_cacheinfo.c |2 +-
arch/x86/mm/tlb.c |2 +-
arch/x86/platform/sfi/sfi.c |2 +-
3 files changed,
Hello Amnon,
I am a bit confused,
On 11/23, Amnon Shiloh wrote:
>
> What I discovered now, is that PTRACE_SYSCALL (also PTRACE_SINGLESTEP)
> does not work within the vsyscall page, so I cannot trap the kernel-calls
> there (this is very simple to verify using "gdb" or "strace").
Sure, but we alr
On Friday 23 November 2012, James Hogan wrote:
> Subject: [PATCH 1/1] asm-generic/io.h: check CONFIG_VIRT_TO_BUS
>
> Make asm-generic/io.h check CONFIG_VIRT_TO_BUS before defining
> virt_to_bus() and bus_to_virt(), otherwise it's easy to accidentally
> have a silently failing incorrect direct mapp
Below cases are supposed to be valid:
min_uV == max_uV == info->max_uV
min_uV == max_uV == rdev->desc->min_uV
Don't return -EINVAL for above cases.
This patch also includes below cleanups:
- Use rdev_get_drvdata(rdev) instead of rdev->reg_data.
- Remove unnecessary WARN_ON, it looks pointless.
Below equation means the "voltage" is the "smallest" voltage within specific
range.
ret = DIV_ROUND_UP(min - bottom) / step;
voltage = ret * step + bottom;
If we do try 1 down when (voltage > max), new voltage is then less than min
voltage. Which means the new voltage is not in the requested volt
forgot to mention...
On 11/23, Oleg Nesterov wrote:
>
> On 11/23, Amnon Shiloh wrote:
> >
> > Or, there is an alternative: if only I (the ptracer or the traced process)
> > was allowed to munmap the vsyscall page,
>
> It is not possible to unmap it. The kernel (swapper_pg_dir) has this
> mapping,
On 11/23/2012 04:31:19 PM, Paul Bolle wrote:
On Fri, 2012-11-23 at 15:42 +0100, Helmut Jarausch wrote:
> with 3.7_rc6 and
>
> CONFIG_ACPI_VIDEO=m
> CONFIG_DRM=y
> CONFIG_DRM_KMS_HELPER=y
> CONFIG_DRM_TTM=y
> CONFIG_DRM_NOUVEAU=y
> CONFIG_NOUVEAU_DEBUG=5
> CONFIG_NOUVEAU_DEBUG_DEFAULT=3
> CONFIG_D
When toying around with debugfs, intentionally trying to break things,
I managed to get it into a reproducible endless loop when cleaning up.
debugfs_remove_recursive() completely ignores that entries found
on ->d_subdirs may already be d_delete()d, but not yet d_kill()ed.
In this case, the firs
Blank lines around braces are not unnecessary.
Emit a message on the use of these blank lines only when
using --strict.
int foo(int bar)
{
something or other
}
is generally written in the kernel as:
int foo(int bar)
{
something or other...
}
Signed-off-by: Joe Perches
---
On Fri, Nov 23, 2012 at 09:21:44PM +0530, viresh kumar wrote:
> On Fri, Nov 23, 2012 at 8:38 PM, Davide Ciminaghi wrote:
> > From: Alessandro Rubini
> >
> > This driver would not compile if ARM_AMBA is selected under x86,
> > because "CS" and "DS" are already defined there. But AMBA
> > is used
On 23 November 2012 22:53, Davide Ciminaghi wrote:
> I tried that, but the resulting patch does not apply:
It will not. Git doesn't support it.
> $ git checkout -b pl330_test next-20121115
> Switched to a new branch 'pl330_test'
>
> $ git format-patch --word-diff 5f1e3c5~..5f1e3c5
I never asked
On 23 November 2012 15:11, Grant Likely wrote:
> On Fri, 23 Nov 2012 00:26:20 +0530, Viresh Kumar
> wrote:
>> + - irq-trigger : IRQ trigger to use for the interrupt
>> to the host
>> + - irq-invert-polarity : bool, IRQ line is connected with
>> reversed pol
On 11/22/2012 01:47 PM, Christoph Hellwig wrote:
> On Wed, Nov 21, 2012 at 04:40:40PM -0600, Dave Kleikamp wrote:
>> It introduces new file ops, read_iter() and write_iter(), that replace the
>> aio_read() and aio_write() operations. The iov_iter structure can now contain
>> either a user-space iov
On 11/23/2012 02:14 AM, Christoph Hellwig wrote:
> On Wed, Nov 21, 2012 at 04:40:41PM -0600, Dave Kleikamp wrote:
>> From: Zach Brown
>>
>> This moves the iov_iter functions in to their own file. We're going to
>> be working on them in upcoming patches. They become sufficiently large,
>> and rem
On 11/23, Pavel Emelyanov wrote:
>
> On 11/22/2012 08:12 PM, Oleg Nesterov wrote:
>
> > Sure. You shouldn't try to save/restore this page(s) directly. But
> > I do not really understand why do you need. IOW, I don't really
> > understand the problem, it depends on what c/r actually does.
>
> Think
Amnon,
I am going to "ignore" this thread because this is not my area and
I can't help anyway. Just one note:
On 11/23, Amnon Shiloh wrote:
>
> The solution can be to hold all catched signals while in the VDSO page.
> ...
>
> 1) + introduce a kernel feature to prevent
>catching signals within
On 11/23/2012 02:19 AM, Christoph Hellwig wrote:
> On Wed, Nov 21, 2012 at 04:40:49PM -0600, Dave Kleikamp wrote:
>> From: Zach Brown
>>
>> __blockdev_direct_IO() had two instances of the same code to determine
>> if a given offset wasn't aligned first to the inode's blkbits and then
>> to the u
On Fri, 2012-11-23 at 18:13 +0100, Helmut Jarausch wrote:
> On 11/23/2012 04:31:19 PM, Paul Bolle wrote:
> > On Fri, 2012-11-23 at 15:42 +0100, Helmut Jarausch wrote:
> > > with 3.7_rc6 and
> > >
> > > CONFIG_ACPI_VIDEO=m
> > > CONFIG_DRM=y
> > > CONFIG_DRM_KMS_HELPER=y
> > > CONFIG_DRM_TTM=y
> > >
Consider the following sequence of operations for a hotplugged memory device:
1. echo "PNP0C80:XX" > /sys/bus/acpi/drivers/acpi_memhotplug/unbind
2. echo "PNP0C80:XX" > /sys/bus/acpi/drivers/acpi_memhotplug/bind
3. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject
The driver is successfully re-bound
On 11/23/2012 02:21 AM, Christoph Hellwig wrote:
> On Wed, Nov 21, 2012 at 04:41:03PM -0600, Dave Kleikamp wrote:
>> swap_writepage can now call nfs's write_iter f_op, eliminating the need to
>> implement for the special-case direct_IO a_op. There is no longer a need to
>> pass the uio flag through
As discussed in https://patchwork.kernel.org/patch/1581581/
the driver core remove function needs to always succeed. This means we need
to know that the device can be successfully removed before acpi_bus_trim /
acpi_bus_hot_remove_device are called. This can cause panics when OSPM-initiated
or SCI
This function should be registered for devices that need to execute some
non-acpi related action in order to be safely removed. If this function
returns zero, the acpi core can continue with removing the device.
Make acpi_bus_remove call the device-specific prepare_remove callback before
removing
Offlining and removal of memory is now done in the prepare_remove callback,
not in the remove callback.
The prepare_remove callback will be called when trying to remove a memory device
with the following ways:
1. send eject request by SCI
2. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject
Note tha
On 11/22/2012 04:59 PM, Dave Chinner wrote:
> On Thu, Nov 22, 2012 at 09:51:33AM +, Steven Whitehouse wrote:
>> Hi,
>>
>> On Wed, 2012-11-21 at 16:41 -0600, Dave Kleikamp wrote:
>>> Signed-off-by: Dave Kleikamp
>>> Cc: Steven Whitehouse
>>> Cc: cluster-de...@redhat.com
>>> ---
>>> fs/gfs2/fi
On Thu, Nov 22, 2012 at 11:29 PM, Stefan Hajnoczi wrote:
> On Wed, Nov 21, 2012 at 03:36:50PM -0800, Vincent Li wrote:
>> We have users running on redhat based distro (Kernel
>> 2.6.32-131.21.1.el6.x86_64 ) with kvm, when customer made cron job
>> script to copy large files between kvm guest or so
This patch correct tty serial drivers.
Unfortunately, many drivers indirectly call ldisc's flush_buffer() function
in own callback function close(). Рarticularly, by the use of tty_ldisc_flush(),
before TTY LAYER calls ldisc's flush_buffer() in the right moment.
1. It disturb the logic of work l
Hello Kees, all,
Please have a look at a *NEW* patch at the end of this mail. It seems to fix
both the issues, stack disclosure + undue recursions.
It uses modprobe "--first-time" option which returns an error code when trying
to load a module which is already present or unload one which is
From: Andreas Larsson
Date: Fri, 23 Nov 2012 12:24:09 +0100
> This bug-fix makes sure that of_iomap is defined extern for sparc so that the
> sparc-specific implementation of_iomap is once again used when including
> include/linux/of_address.h in a sparc context. OF_GPIO that is now available
>
From: Paolo Valente
Date: Thu, 22 Nov 2012 17:56:20 +0100
> +/*
> +
> + */
Please don't add useless things like this in your patch.
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
From: Nicolas Ferre
Date: Fri, 23 Nov 2012 14:49:01 +0100
> Add information to the DMA Configuration Register to
> maximize system performance:
> - rx/tx packet buffer full memory size
> - allow possibility to use INCR16 if supported
>
> Signed-off-by: Nicolas Ferre
Applied to net-next.
--
To
Coming a bit late to the -rc party, but here are some bug fixes found
recently through testing, regular usages, and code inspection.
Most worrying is a data corruption risk when 'replacing' devices in a RAID10.
Maybe most interesting is that generic DISCARD support requires granularity to
be a po
Please pull in this bug fix from Al Viro.
Thanks!
The following changes since commit 3587b1b097d70c2eb9fee95ea7995d13c05f66e5:
fanotify: fix FAN_Q_OVERFLOW case of fanotify_read() (2012-11-18 09:30:00
-1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kerne
On Friday, November 23, 2012 01:42:21 PM Fabio Baltieri wrote:
> Hi Rafael,
>
> On Fri, Nov 23, 2012 at 10:31:56AM +0100, Fabio Baltieri wrote:
> > drivers/cpufreq/cpufreq_ondemand.c | 152
> > -
> > 1 file changed, 132 insertions(+), 20 deletions(-)
>
> I ju
On Fri, Nov 23, 2012 at 07:23:28PM +0530, Viresh Kumar wrote:
> On 23 November 2012 18:42, Fabio Baltieri wrote:
> > Restore the correct delay value for ondemand's od_dbs_timer, as it was
> > changed erroneously in 83f0e55.
> >
> > Cc: Viresh Kumar
> > Signed-off-by: Fabio Baltieri
> > ---
> >
Networking bug fixes, Cacio e Pepe edition:
1) BNX2X accidently accesses chip rev specific registers without
an appropriate guard, fix from Ariel Elior.
2) When we removed the routing cache, we set ip_rt_max_size to
~0 just to keep reporting a value to userspace via sysfs.
But the ipv4
Option parsing code expects an unsigned integer for the codepage option,
but prefixes and stores this option with "cp" before passing to
load_nls(). This makes the displayed option in /proc an invalid one.
Strip the prefix when printing so that the displayed option is valid
for reuse.
Signed-off-b
Daniel Kiper writes:
> On Thu, Nov 22, 2012 at 04:15:48AM -0800, ebied...@xmission.com wrote:
>>
>> Is this for when the hypervisor crashes and we want a crash dump of
>> that?
>
> dom0 at boot gets some info about kexec/kdump configuration from Xen
> hypervisor
> (e.g. placement of crash kernel
Hello.
Srikar, it is not clear if you was convinced or not during the
last discussion. We will discuss this again probably. So far
I am sending the initial changes which (I think) make sense in
any case. Please review.
The next step is locking. Alas, we can not use consumer_rwsem
to protect the l
Cosmetic. __set_bit(UPROBE_SKIP_SSTEP) is the part of initialization,
it is not clear why it is set in insert_uprobe().
Signed-off-by: Oleg Nesterov
---
kernel/events/uprobes.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/kernel/events/uprobes.c b/kernel/events/up
Add the new helper filter_chain(). Currently it is only placeholder,
the comment explains what is should do. We will change it later to
consult every consumer to decide whether we need to install the swbp.
Until then it works as if any consumer returns true, this matches the
current behavior.
Chan
To support the filtering uprobe_register() should do
register_for_each_vma(true) every time the new consumer comes,
we need to install the previously nacked breakpoints.
Note:
- uprobes_mutex[] should die, what is actually protects is
alloc_uprobe().
- UPROBE_RUN_HANDLER
register/unregister verifies that inode/uc != NULL. For what?
This really looks like "hide the potential problem", the caller
should pass the valid data.
register() also checks uc->next == NULL, probably to prevent the
double-register but the caller can do other stupid/wrong things.
If we do this
Trivial. uprobe can't be NULL after mutex_unlock(), it was already used.
Signed-off-by: Oleg Nesterov
---
kernel/events/uprobes.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
index e9f22ed..13b247c 100644
--- a/kerne
uprobe_consumer->filter() is pointless in its current form, kill it.
We will add it back, but with the different signature/semantics. Perhaps
we will even re-introduce the callsite in handler_chain(), but not to
just skip uc->handler().
Signed-off-by: Oleg Nesterov
---
include/linux/uprobes.h
uprobe_unregister() removes the breakpoints only if the last consumer
goes away. To support the filtering it should do this every time, we
want to remove the breakpoints which nobody else want to keep.
Note: given that filter_chain() is not actually implemented, this patch
itself doesn't change th
On Friday, November 23, 2012 01:35:58 PM Adrian Hunter wrote:
> Hi
>
> Here is SDHCI ACPI driver.
>
> Changes for v2:
>
> Dropped "PNPACPI: exclude SDHCI devices"
> Added "PNPACPI: exclude devices already bound"
> Changed dev->acpi_handle to ACPI_HANDLE(dev)
> Added Chris
On Friday, November 23, 2012 08:57:02 PM Fabio Baltieri wrote:
> On Fri, Nov 23, 2012 at 07:23:28PM +0530, Viresh Kumar wrote:
> > On 23 November 2012 18:42, Fabio Baltieri wrote:
> > > Restore the correct delay value for ondemand's od_dbs_timer, as it was
> > > changed erroneously in 83f0e55.
> >
Hi,
when compiling a kernel with the gold linker (3.7.0-rc6 26d29d06ea0204,
gcc-4.7 and binutils-2.23 in my case), certain pcpu symbols are
seemingly errneously copied over from .o files to .ko files, leading to
a hard warning during depmod:
gold$ make -j8 LD=gold HOSTLD=gold
201 - 300 of 393 matches
Mail list logo
