3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 48c3375c5f69b1c2ef3d1051a0009cb9bce0ce24 upstream.
This patch (as1640) fixes a memory leak in xhci-hcd. The urb_priv
data structure isn't always deallocated in the
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Daniele Palmas
commit 78796ae17eacedcdcaaeb03ba73d2e532a4c8f83 upstream.
Add VID and PID for Telit Gobi QDL device
Signed-off-by: Daniele Palmas
Signed-off-by: Greg Kroah-Hartman
---
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Luebbe
commit 72fca4a4b32dc778b5b885c3498700e42b610d49 upstream.
Previously the alarm event was not propagated into the RTC subsystem.
By adding a call to rtc_update_irq, this fixes a
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: fangxiaozhi
commit 200e0d994d9d1919b28c87f1a5fb99a8e13b8a0f upstream.
1. Optimize the match rules with new macro for Huawei USB storage devices,
to avoid to load USB storage driver for the
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit fd5d93a0015ce1a7db881382022b2fcdfdc61760 upstream.
If the requested number of DWs on the ring is larger than
the size of the ring itself, return an error.
In testing with
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 9200ee4941a6e5d1ec5df88982243686882dff3f upstream.
vbios says external TMDS while the board is actually
internal TMDS.
fixes:
:3556:26: error: 'const struct snd_soc_dai_ops' has no
member named 'mute_stream'
Caused by commit df6dc7a26e7d ("ASoC: core: Allow digital mute for
capture").
I have used the sound-asoc tree from next-20130207 for today.
--
Cheers,
Stephen Rothwells...@canb.a
On Thu, Feb 7, 2013 at 10:13 PM, Andrey Wagin wrote:
> 2013/2/7 Oleg Nesterov :
>> Andrey, sorry for delay.
>>
>> As for API, I leave this to you and Michael. Not that I like these
>> new flags, but I agree that pread() hack was not pretty too.
>>
>> On 01/29, Andrey Vagin wrote:
[...]
>>Damn.
Hi Toshi,
2013/02/07 7:50, Toshi Kani wrote:
> Changed sysfs eject, acpi_eject_store(), to support ACPI scan handlers.
>
> Signed-off-by: Toshi Kani
> ---
> drivers/acpi/scan.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/scan.c
Hi Linus,
On Mon, Jan 07, 2013 at 03:38:21PM +0100, Linus Walleij wrote:
> >> what is the status on the HSI subsystem? We have based some patches for
> >> HSI master on top of the OMAP HSI master patches, but these never seem
> >> to reach the tree?
> >
> > Ping on the cch.devel address
On Thu, Feb 07, 2013 at 04:03:54PM -0800, Eric Dumazet wrote:
> On Thu, 2013-02-07 at 15:58 -0800, Michel Lespinasse wrote:
>
> > No, I think that's doable. The trick would be that once a thread
> > acquires the lock, the only remaining use of the node is to receive
> > the 'next' pointer if/when
On 02/07/2013 02:09 AM, Linus Walleij wrote:
> On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart wrote:
>
>> Is it that some other driver has claimed these GPIO lines? If so, how do
>> I determine which one?
>
> Yes I think that could be it, the driver would need to call
> gpio_export() for it to
On Tue, 5 Feb 2013, Mel Gorman wrote:
> On Fri, Jan 25, 2013 at 06:00:50PM -0800, Hugh Dickins wrote:
> > In some places where get_ksm_page() is used, we need the page to be locked.
> >
> > When KSM migration is fully enabled, we shall want that to make sure that
> > the page just acquired cannot
On Thu, Feb 7, 2013 at 7:20 PM, Oleg Nesterov wrote:
> Michael, thanks for your attention.
>
> On 01/23, Michael Kerrisk (man-pages) wrote:
>>
>> SFD_RAW -- return raw siginfo structs when reading, rather than
>> signalfd_siginfo
>
> I hope you are going to document this API... Then please note
On Thu, Feb 07, 2013 at 02:15:02PM -0800, Andrew Morton wrote:
> On Thu, 7 Feb 2013 16:57:42 -0500
> Josh Boyer wrote:
>
> > Hi All,
> >
> > We've hit a weird error in Fedora using the 3.8-rcX kernels. It seems
> > the mock tool is getting back ENOMEM when doing very simple things that
> >
On Thu, Feb 7, 2013 at 2:34 PM, Paul E. McKenney
wrote:
> On Tue, Jan 22, 2013 at 03:13:30PM -0800, Michel Lespinasse wrote:
>> Introduce queue spinlocks, to be used in situations where it is desired
>> to have good throughput even under the occasional high-contention situation.
>>
>> This
On Thu, Feb 7, 2013 at 7:17 PM, Oleg Nesterov wrote:
> AOn 01/22, Andrey Vagin wrote:
>>
>> This patch is added two flags SFD_SHARED_QUEUE and SFD_PER_THREAD_QUEUE
>> SFD_SHARED_QUEUE
>
> I can't believe I am going to blame the naming ;) but these 2 do not look
> "symmetrical"
>
>
> From: kexec-boun...@lists.infradead.org
> Sent: Friday, February 08, 2013 9:26 AM
> > From: Vivek Goyal [mailto:vgo...@redhat.com]
> > Sent: Friday, February 08, 2013 12:06 AM
>
> > On Wed, Feb 06, 2013 at 07:24:46AM +, Hatayama, Daisuke wrote:
> > > From: Vivek Goyal
> > > Subject: Re:
> From: Vivek Goyal [mailto:vgo...@redhat.com]
> Sent: Friday, February 08, 2013 12:06 AM
> On Wed, Feb 06, 2013 at 07:24:46AM +, Hatayama, Daisuke wrote:
> > From: Vivek Goyal
> > Subject: Re: [PATCH] kdump, oldmem: support mmap on /dev/oldmem
> > Date: Tue, 5 Feb 2013 10:12:56 -0500
> >
>
On Monday, February 04, 2013 12:47:31 AM Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The only useful thing that the ACPI container driver does is to
> install system notify handlers for all container and module device
> objects it finds in the namespace. The driver structure,
>
From: Rafael J. Wysocki
Make the ACPI container driver use struct acpi_scan_handler for
representing the object used to initialize ACPI containers and remove
the ACPI driver structure used previously and the data structures
created by it, since in fact they were not used for any purpose.
This
From: Rafael J. Wysocki
Since the FORCE_EJECT symbol is never defined, the
#ifndef FORCE_EJECT in acpi_eject_store() is always true, so drop it.
Signed-off-by: Rafael J. Wysocki
---
drivers/acpi/scan.c |2 --
1 file changed, 2 deletions(-)
Index: test/drivers/acpi/scan.c
> When using the sata_mv driver, I can't see my drives.
>
> The drives are SATA6Gbps.
>
> The SATA card is a Supermicro AOC-SAT2-MV8 SATA3Gbps card with a
Marvell
> 88SX6081 chip onboard.
Never mind, old kernel. Fixed in 3.7.6. Sorry for the noise.
--
To unsubscribe from this list: send the
The latest maintenance release Git v1.8.1.3 is now available at
the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
29ed9047263f9835726200226451339276641779 git-1.8.1.3.tar.gz
On Tue, 5 Feb 2013, Mel Gorman wrote:
> On Fri, Jan 25, 2013 at 05:59:35PM -0800, Hugh Dickins wrote:
> > Memory hotremove's ksm_check_stable_tree() is pitifully inefficient
> > (restarting whenever it finds a stale node to remove), but rearrange
> > so that at least it does not needlessly restart
On Sun, 03 Feb 2013 21:13:36 +0800
Zhang Yanfei wrote:
> From: Zhang Yanfei
>
> In function read_vmcore, two if tests are duplicate. Change the position
> of them could reduce the duplication. This change does not affect
> the behaviour of the function.
>
hm, yes.
> --- a/fs/proc/vmcore.c
>
On Thu, 2013-02-07 at 15:58 -0800, Michel Lespinasse wrote:
> No, I think that's doable. The trick would be that once a thread
> acquires the lock, the only remaining use of the node is to receive
> the 'next' pointer if/when another thread starts contending for the
> lock. So if the lock state
On Thu, Feb 7, 2013 at 2:56 PM, Eric Dumazet wrote:
> On Thu, 2013-02-07 at 14:34 -0800, Paul E. McKenney wrote:
>> On Tue, Jan 22, 2013 at 03:13:30PM -0800, Michel Lespinasse wrote:
>> > Introduce queue spinlocks, to be used in situations where it is desired
>> > to have good throughput even
On Tue, 5 Feb 2013, Mel Gorman wrote:
> On Fri, Jan 25, 2013 at 05:54:53PM -0800, Hugh Dickins wrote:
> > From: Petr Holasek
> >
> > Introduces new sysfs boolean knob /sys/kernel/mm/ksm/merge_across_nodes
> > which control merging pages across different numa nodes.
> > When it is set to zero
On Thu, Feb 07, 2013 at 11:58:09PM +0100, Samuel Ortiz wrote:
> On Thu, Feb 07, 2013 at 10:38:44PM +, Arnd Bergmann wrote:
> > On Thursday 07 February 2013, Tomas Winkler wrote:
> > >
> > > +inline void *mei_bus_get_clientdata(const struct mei_bus_client *client)
> > > +{
> > > + return
On Thu, Feb 07, 2013 at 02:56:49PM -0800, Eric Dumazet wrote:
> On Thu, 2013-02-07 at 14:34 -0800, Paul E. McKenney wrote:
> > On Tue, Jan 22, 2013 at 03:13:30PM -0800, Michel Lespinasse wrote:
> > > Introduce queue spinlocks, to be used in situations where it is desired
> > > to have good
On Thursday 07 February 2013, Rob Herring wrote:
> How so? I don't see a warning as there is no type checking on the init
> function since of_device_id.data is just a void *. It would be good to
> have type checking here if you know a way, but I don't.
Ah, that's right. So it silently builds find
On Friday, February 08, 2013 12:33:14 AM Rafael J. Wysocki wrote:
> On Thursday, February 07, 2013 03:57:42 PM Viresh Kumar wrote:
> > Hi Rafael,
> >
> > This is another unplanned patchset for all the platforms that i broke. :)
> >
> > Okay, there are two important fixes (1 & 4) and two general
On Tue, 5 Feb 2013 10:12:03 +0100
Lukas Czerner wrote:
> This commit changes truncate_inode_pages_range() so it can handle non
> page aligned regions of the truncate. Currently we can hit BUG_ON when
> the end of the range is not page aligned, but we can handle unaligned
> start of the range.
>
On 02/07/2013 04:44 PM, Arnd Bergmann wrote:
> On Thursday 07 February 2013, Rob Herring wrote:
>> From: Rob Herring
>>
>> In the recently added support for OF based clocksource init, a device node
>> will be matched twice. We can fix this by passing the device node to the
>> init functions and
On 07/02/13 23:44, Andrew Morton wrote:
So please update the changelog and then cc net...@vger.kernel.org on
the patch - the netdev people are probably best-situated to comment on
the proposal.
OK. Done. Thanks for the advice!
Martin
--
To unsubscribe from this list: send the line
On 02/07/2013 10:46 PM, Joe Perches wrote:
> alloc failures already get standardized OOM
> messages and a dump_stack.
>
> For the affected mallocs around these OOM messages:
>
> Converted kmallocs with multiplies to kmalloc_array.
> Converted a kmalloc/memcpy to kmemdup.
> Removed now unused
When implementing network protocols in user space, one has to implement
fake user-space file descriptors to represent the sockets for the protocol.
While all the BSD socket API functionality for such descriptors may be faked as
well (myproto_send(), myproto_recv() etc.) this approach doesn't work
Am Thu, 07 Feb 2013 15:49:58 -0700
schrieb Alex Williamson :
> > If I whitelist pcieport USB3 works within the guests. :-)
> > Binding 1c.0 and 1c.6 is no longer needed.
> > Next week I'll run some more tests with USB3 devices.
>
> Great! Thanks for the test. I assume you didn't need to do
On Thursday, February 07, 2013 03:57:42 PM Viresh Kumar wrote:
> Hi Rafael,
>
> This is another unplanned patchset for all the platforms that i broke. :)
>
> Okay, there are two important fixes (1 & 4) and two general cleanups (2 & 3).
> I
> hope most of the issues would be resolved by these
On Thu, 07 Feb 2013 09:57:27 +0800
Zhang Yanfei wrote:
> Functions nr_free_zone_pages, nr_free_buffer_pages and nr_free_pagecache_pages
> are horribly badly named, so accurately document them with code comments
> in case of the misuse of them.
Looks OK. I fiddled with it a bit:
---
On Tuesday, February 05, 2013 08:04:50 PM Nathan Zimmer wrote:
> In general rwlocks are discourged so we are moving it to use the rcu instead.
>
> Cc: Viresh Kumar
> Cc: "Rafael J. Wysocki"
> Signed-off-by: Nathan Zimmer
> ---
> drivers/cpufreq/cpufreq.c | 173
>
On 01/31/2013 01:14 PM, Christopher Heiny wrote:
On 01/31/2013 12:08 AM, Dmitry Torokhov wrote:
Hi Chris,
On Fri, Jan 18, 2013 at 05:12:44PM -0800, Christopher Heiny wrote:
In addition to the changes described in 0/0 of this patchset, this patch
includes device serialization updated to
On 02/07/2013 02:34 PM, Paul E. McKenney wrote:
On Tue, Jan 22, 2013 at 03:13:30PM -0800, Michel Lespinasse wrote:
Introduce queue spinlocks, to be used in situations where it is desired
to have good throughput even under the occasional high-contention situation.
This initial implementation is
On Wed, 06 Feb 2013 22:48:08 +0800
Jeremy Kerr wrote:
> This change adds a few initial efivarfs tests to the
> tools/testing/selftests directory.
>
> The open-unlink test is based on code from
> Lingzhu Xiang .
>
> ...
>
> --- a/tools/testing/selftests/Makefile
> +++
On Thursday 07 February 2013, Michal Simek wrote:
> Subject: "asm-generic: io: Fix ioread16/32be and iowrite16/32be"
Ok, thanks. If you don't mind, I think this can just go with the other patches
for xsysace that come out of this discussion.
Arnd
--
To unsubscribe from this list: send
On Thursday 07 February 2013, Winkler, Tomas wrote:
> Second why to register anything if the MEI device is not present on the
> system.
Mostly to match the expectations of readers of that code. Note that no memory
is wasted if you do this, because it's a static data structure. You can
actually
> -Original Message-
> From: Samuel Ortiz [mailto:sa...@linux.intel.com]
> Sent: Friday, February 08, 2013 00:59
> To: Arnd Bergmann
> Cc: Winkler, Tomas; gre...@linuxfoundation.org; linux-
> ker...@vger.kernel.org
> Subject: Re: [char-misc-next 01/11] mei: bus: Initial MEI bus type
>
On Thursday 07 February 2013, Grant Likely wrote:
> On Thu, Feb 7, 2013 at 3:28 PM, Alexey Brodkin
> Starting with register (non-data) access. The bus bindings are such
> that on both BE and LE systems a native 16 bit read results in the
> bits being in the correct order. On powerpc, you want to
On Thu, 2013-02-07 at 23:23 +0100, Richard Weinberger wrote:
> Hi,
>
> Am Wed, 06 Feb 2013 15:45:37 -0700
> schrieb Alex Williamson :
>
> > On Wed, 2013-02-06 at 21:25 +0100, Richard Weinberger wrote:
> > > Hi,
> > >
> > > Am Wed, 06 Feb 2013 11:47:20 -0700
> > > schrieb Alex Williamson :
> >
On Thursday, February 07, 2013 06:52:20 PM Viresh Kumar wrote:
> On 7 February 2013 18:35, Rafael J. Wysocki wrote:
> > I think they all make sense, so applied to linux-next.
> >
> > I would prefer not to make any more changes to cpufreq before v3.9 from now
> > on,
> > except for fixes and
On Thu, Feb 07, 2013 at 10:41:06PM +, Arnd Bergmann wrote:
> On Thursday 07 February 2013, Tomas Winkler wrote:
> > +}
> > +EXPORT_SYMBOL(mei_add_device);
> > +
> > +void mei_remove_device(struct mei_bus_client *client)
> > +{
> > + device_unregister(>dev);
> > +}
> >
On Thu, Feb 07, 2013 at 10:38:44PM +, Arnd Bergmann wrote:
> On Thursday 07 February 2013, Tomas Winkler wrote:
> >
> > +inline void *mei_bus_get_clientdata(const struct mei_bus_client *client)
> > +{
> > + return dev_get_drvdata(>dev);
> > +}
> > +EXPORT_SYMBOL(mei_bus_get_clientdata);
Hi Arnd,
On Thu, Feb 07, 2013 at 10:37:30PM +, Arnd Bergmann wrote:
> On Thursday 07 February 2013, Tomas Winkler wrote:
> > @@ -197,6 +197,9 @@ static int mei_probe(struct pci_dev *pdev, const struct
> > pci_device_id *ent)
> > mei_pdev = pdev;
> > pci_set_drvdata(pdev,
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: Friday, February 08, 2013 00:38
> To: Winkler, Tomas
> Cc: gre...@linuxfoundation.org; sa...@linux.intel.com; linux-
> ker...@vger.kernel.org
> Subject: Re: [char-misc-next 05/11] mei: bus: Call bus routines from
On Thu, 2013-02-07 at 14:34 -0800, Paul E. McKenney wrote:
> On Tue, Jan 22, 2013 at 03:13:30PM -0800, Michel Lespinasse wrote:
> > Introduce queue spinlocks, to be used in situations where it is desired
> > to have good throughput even under the occasional high-contention situation.
> >
> > This
Hi Arnd,
On Thu, Feb 07, 2013 at 10:34:44PM +, Arnd Bergmann wrote:
> On Thursday 07 February 2013, Tomas Winkler wrote:
> > +
> > +struct mei_bus_ops {
> > + int (*send)(struct mei_bus_client *client, u8 *buf, size_t length);
> > + int (*recv)(struct mei_bus_client *client, u8
When building the driver, gcc emits the following warnings:
.../drivers/staging/goldfish/goldfish_nand.c:
In function 'goldfish_nand_read_oob':
goldfish_nand.c:159:2:
warning: format '%x' expects argument of type 'unsigned int', but
argument 3 has type 'size_t' [-Wformat]
goldfish_nand.c:159:2:
On Thursday 07 February 2013, Rob Herring wrote:
> From: Rob Herring
>
> In the recently added support for OF based clocksource init, a device node
> will be matched twice. We can fix this by passing the device node to the
> init functions and removing the match functions within the init
On Thu, 7 Feb 2013 07:41:32 +0100
Martin Sustrik wrote:
> When implementing network protocols in user space, one has to implement
> fake user-space file descriptors to represent the sockets for the protocol.
>
> While all the BSD socket API functionality for such descriptors may be faked
> as
On Tue, Jan 22, 2013 at 03:13:30PM -0800, Michel Lespinasse wrote:
> Introduce queue spinlocks, to be used in situations where it is desired
> to have good throughput even under the occasional high-contention situation.
>
> This initial implementation is based on the classic MCS spinlock,
>
If CONFIG_MTD is not set goldfish_nand fails to compile with the
following linker warnings:
drivers/built-in.o: In function `goldfish_nand_remove':
goldfish_nand.c:(.text+0x6e7d0e): undefined reference to
`mtd_device_unregister'
drivers/built-in.o: In function `goldfish_nand_erase':
Hi Arnd,
On Thu, Feb 07, 2013 at 10:26:42PM +, Arnd Bergmann wrote:
> On Thursday 07 February 2013, Tomas Winkler wrote:
> >
> > From: Samuel Ortiz
> >
> > NFC ME client is exported through mei bus to be consumed by the
> > NFC subsystem.
> >
> > NFC is represented by two mei clients: An
On Thursday 07 February 2013, Tomas Winkler wrote:
> +}
> +EXPORT_SYMBOL(mei_add_device);
> +
> +void mei_remove_device(struct mei_bus_client *client)
> +{
> + device_unregister(>dev);
> +}
> +EXPORT_SYMBOL(mei_remove_device);
One more point: did you intentionally pick EXPORT_SYMBOL over
On Thursday 07 February 2013, Tomas Winkler wrote:
>
> +inline void *mei_bus_get_clientdata(const struct mei_bus_client *client)
> +{
> + return dev_get_drvdata(>dev);
> +}
> +EXPORT_SYMBOL(mei_bus_get_clientdata);
> +
Did you really mean to export an inline function?
Can you make this a
On Thursday 07 February 2013, Tomas Winkler wrote:
> @@ -197,6 +197,9 @@ static int mei_probe(struct pci_dev *pdev, const struct
> pci_device_id *ent)
> mei_pdev = pdev;
> pci_set_drvdata(pdev, dev);
>
> + err = mei_bus_init(mei_pdev);
> + if (err)
> +
On Thursday, February 07, 2013 07:32:26 PM Viresh Kumar wrote:
> On Thu, Feb 7, 2013 at 4:12 PM, Viresh Kumar wrote:
> > @Rafael: I wasn't sure if these would apply over my patches without any
> > conflicts and so i applied them in my repo. Added my Acked-by's and fixed
> > a minor thing in one
On Thursday, February 07, 2013 07:32:07 AM Toshi Kani wrote:
> On Thu, 2013-02-07 at 02:32 +0100, Rafael J. Wysocki wrote:
> > On Wednesday, February 06, 2013 05:51:42 PM Toshi Kani wrote:
> > > On Thu, 2013-02-07 at 01:55 +0100, Rafael J. Wysocki wrote:
> > > > On Wednesday, February 06, 2013
On Thursday 07 February 2013, Tomas Winkler wrote:
> +
> +struct mei_bus_ops {
> + int (*send)(struct mei_bus_client *client, u8 *buf, size_t length);
> + int (*recv)(struct mei_bus_client *client, u8 *buf, size_t length);
> +};
> +
Can you have more than one set of mei_bus_ops in a
On Thu, 2013-02-07 at 23:33 +0200, Michael S. Tsirkin wrote:
> On Thu, Feb 07, 2013 at 01:14:20PM -0500, David Miller wrote:
> > From: Ben Hutchings
> > Date: Thu, 7 Feb 2013 16:20:46 +
> >
> > > If the consensus is still that we must preserve packets exactly (aside
> > > from the usual
On Thursday 07 February 2013, Tomas Winkler wrote:
> +int mei_add_driver(struct mei_bus_driver *driver)
By convention, I think this should be called mei_driver_register(),
matching what we do on most other subsystem. Similarly
for mei_driver_unregister().
Arnd
--
To unsubscribe from
On Thursday 07 February 2013, Tomas Winkler wrote:
> From: Samuel Ortiz
>
> mei bus will present some of the me clients
> as devices for other standard subsystems
>
> Implement the probe, remove, match and the device addtion routines.
> A mei-bus.txt document describing the rationale and the
On Thursday 07 February 2013, Tomas Winkler wrote:
>
> From: Samuel Ortiz
>
> NFC ME client is exported through mei bus to be consumed by the
> NFC subsystem.
>
> NFC is represented by two mei clients: An info one and the actual
> NFC one. In order for correct connection we first need to
Hi,
Am Wed, 06 Feb 2013 15:45:37 -0700
schrieb Alex Williamson :
> On Wed, 2013-02-06 at 21:25 +0100, Richard Weinberger wrote:
> > Hi,
> >
> > Am Wed, 06 Feb 2013 11:47:20 -0700
> > schrieb Alex Williamson :
> > > Does the card work with pci-assign or are both broken?
> >
> > It works with
On Thu, 2013-02-07 at 23:18 +0100, Rafael J. Wysocki wrote:
> On Thursday, February 07, 2013 02:19:13 PM Toshi Kani wrote:
> > When acpi_device_install_notify_handler() failed in acpi_device_probe(),
> > it calls acpi_drv->ops.remove() and fails the probe. However, the ACPI
> > driver is left
Hi Guenter,
> Signed-off-by: Guenter Roeck
> ---
> drivers/watchdog/Kconfig |1 +
> drivers/watchdog/booke_wdt.c | 185
> +++---
> 2 files changed, 66 insertions(+), 120 deletions(-)
>
Added to linux-watchdog-next.
Kind regards,
Wim.
--
To
On Sun, Jan 13, 2013 at 02:38:20PM +0300, Sergey Senozhatsky wrote:
> On (01/12/13 20:27), Dave Jones wrote:
> > BUG: sleeping function called from invalid context at mm/slub.c:925
> > in_atomic(): 1, irqs_disabled(): 0, pid: 566, name: Xorg
> > INFO: lockdep is turned off.
> > Pid: 566, comm:
On Thu, 7 Feb 2013 16:57:42 -0500
Josh Boyer wrote:
> Hi All,
>
> We've hit a weird error in Fedora using the 3.8-rcX kernels. It seems
> the mock tool is getting back ENOMEM when doing very simple things that
> normally just work. The 3.7 kernels on the same userspace work just
> fine. It
On Thursday, February 07, 2013 02:19:13 PM Toshi Kani wrote:
> When acpi_device_install_notify_handler() failed in acpi_device_probe(),
> it calls acpi_drv->ops.remove() and fails the probe. However, the ACPI
> driver is left bound to the acpi_device. Fix it by clearing the driver
> and
On 02/07/2013 10:46 PM, Joe Perches wrote:
> alloc failures already get standardized OOM
> messages and a dump_stack.
>
> For the affected mallocs around these OOM messages:
>
> Converted kmallocs with multiplies to kmalloc_array.
> Converted a kmalloc/memcpy to kmemdup.
> Removed now unused
Hey, again.
On Fri, Feb 01, 2013 at 02:41:36AM +0800, Lai Jiangshan wrote:
> Every time, when we need to find the executing worker from work,
> we need 2 steps:
> find the pool from the idr by pool id.
> find the worker from the hash table of the pool.
>
> Now we merge them as one
Hi All,
We've hit a weird error in Fedora using the 3.8-rcX kernels. It seems
the mock tool is getting back ENOMEM when doing very simple things that
normally just work. The 3.7 kernels on the same userspace work just
fine. It seems just running 'mock init -v' is enough to cause the
failure.
From: Andi Kleen
Newer gcc enables the var-tracking pass with -g to keep track which
registers contain which variables. This is one of the slower passes in gcc.
With reduced debug info (aimed at objdump -S, but not using a full debugger)
we don't need this fine grained tracking. But it was
alloc failures already get standardized OOM
messages and a dump_stack.
For the affected mallocs around these OOM messages:
Converted kmallocs with multiplies to kmalloc_array.
Converted a kmalloc/memcpy to kmemdup.
Removed now unused stack variables.
Removed unnecessary parentheses.
Neatened
Hi,
On Wed, 06 Feb 2013 13:55:08 -0800 "H. Peter Anvin" wrote:
>
> So why don't we let Linus either accept and reject it for the 3.9 merge,
> but it rejected, we drop it from linux-next until such time as Linus'
> objections have been addressed?
It has been in linux-next since before v3.2. It
On Thu, 07 Feb 2013 20:01:27 +0900
Jonghwa Lee wrote:
> This patch adds rtc driver for Maxim 8997 multifunction chip.
> Max8997 has rtc module in it. and it can be used for timekeeping
> clock and system alarm. It provide various operational mode those are
> BCD/binary, 24/12hour, am/pm. Driver
Hi Ingo,
On Wed, 6 Feb 2013 22:46:46 +0100 Ingo Molnar wrote:
>
> Pekka still intends to send it in the next merge window AFAIK,
That has been true since v3.2 :-(
> and I use it for testing rather frequently so I'm not going to
> remove it from my tree for the time being.
I didn't ask you
Hi Aaro,
> Introduce Retu watchdog driver.
>
> Cc: linux-watch...@vger.kernel.org
> Acked-by: Felipe Balbi
> Acked-by: Tony Lindgren
> Signed-off-by: Aaro Koskinen
> Cc: Wim Van Sebroeck
Added tolinux-watchdog-next.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line
There is a race that can hit during __cleanup() when the ioat->head pointer is
incremented during descriptor submission. The __cleanup() can clear the
PENDING flag when it does not see any active descriptors. This causes new
submitted descriptors to be ignored because the COMPLETION_PENDING flag
On Wed, Feb 6, 2013 at 5:10 PM, Andrew Morton wrote:
> On Wed, 06 Feb 2013 19:39:11 -0500
> Sasha Levin wrote:
>
>> We're now hitting the VM_BUG_ON() which was added in the last hunk of the
>> patch:
>
> hm, why was that added.
>
> Michel, I seem to have confused myself over this series. I saw
On Wed, 30 Jan 2013 21:00:22 -0500
Sasha Levin wrote:
> I'm not sure why, but the hlist for each entry iterators were conceived
> differently from the list ones. While the list ones are nice and elegant:
>
> list_for_each_entry(pos, head, member)
>
> The hlist ones were greedy and
When acpi_device_install_notify_handler() failed in acpi_device_probe(),
it calls acpi_drv->ops.remove() and fails the probe. However, the ACPI
driver is left bound to the acpi_device. Fix it by clearing the driver
and driver_data fields.
Signed-off-by: Toshi Kani
---
This patch is based on
On Thu, Feb 07, 2013 at 01:14:20PM -0500, David Miller wrote:
> From: Ben Hutchings
> Date: Thu, 7 Feb 2013 16:20:46 +
>
> > If the consensus is still that we must preserve packets exactly (aside
> > from the usual modifications by IP routers) then LRO should be disabled
> > on all devices
> The kernel build will be sad on !SMP configs.
Good catch, thank you. Here is a new version.
---8<---
Subject: x86,smp: limit spinlock delay on virtual machines
Modern Intel and AMD CPUs will trap to the host when the guest
is spinning on a spinlock, allowing the host to schedule in
On Thu, Feb 07, 2013 at 09:02:38PM +, David Woodhouse wrote:
> Backtraces add visibility and have proven to be extremely useful in the
> past for getting people to actually *fix* broken BIOSes.
>
> When kerneloops.org was running, it also gave very good statistics which
> helped to apply
2013/2/7 Oleg Nesterov :
> Andrey, sorry for delay.
>
> As for API, I leave this to you and Michael. Not that I like these
> new flags, but I agree that pread() hack was not pretty too.
>
> On 01/29, Andrey Vagin wrote:
>> +static ssize_t signalfd_peek(struct signalfd_ctx *ctx,
>> +
On Thu, 2013-02-07 at 20:56 +0400, Alexey Brodkin wrote:
> > So, if I'm correct that means that for the data port (specifically
> > copying between RAM and the data port) using ioread16/iowrite16 on the
> > data port results in the correct behaviour. It also means that LE
> > support in the
On Thu, 2013-02-07 at 16:44 +, Grant Likely wrote:
>
> I've just spent some quality time with a piece of paper, and I think
> I've figured it out...
http://linuxplumbers.ubicast.tv/videos/big-and-little-endian-inside-out/
Watch the last part on IO busses
This all has to do which which
From: Lai Jiangshan
Currently, __queue_work() chooses the pool to queue a work item to and
then determines cwq from the target wq and the chosen pool. This is a
bit backwards in that we can determine cwq first and simply use
cwq->pool. This way, we can skip get_std_worker_pool() in queueing
On Thu, 2013-02-07 at 15:23 +, Grant Likely wrote:
>
> Maybe. In a separate patch. Hmmm... I guess there isn't an
> ioread16be_rep variant.
Because it would not make sense. The ioread16_rep isn't "LE" ... it
should be usable for any kind if data port since such a fifo should
never require
201 - 300 of 1490 matches
Mail list logo
