On Fri, 2013-11-22 at 19:19 -0800, Davidlohr Bueso wrote:
> On Fri, 2013-11-22 at 17:25 -0800, Linus Torvalds wrote:
> > On Fri, Nov 22, 2013 at 4:56 PM, Davidlohr Bueso wrote:
> > > In futex_wake() there is clearly no point in taking the hb->lock if
> > > we know beforehand that there are no
On Fri, 2013-11-22 at 16:56 -0800, Davidlohr Bueso wrote:
> In futex_wake() there is clearly no point in taking the hb->lock if
> we know beforehand that there are no tasks to be woken. This comes
> at the smaller cost of doing some atomic operations to keep track of
> the list's size.
On Fri, 2013-11-22 at 16:56 -0800, Davidlohr Bueso wrote:
> Currently, the futex global hash table suffers from it's fixed, smallish
> (for today's standards) size of 256 entries, as well as its lack of NUMA
> awareness. Large systems, using many futexes, can be prone to high amounts
> of
On Fri, 2013-11-22 at 16:56 -0800, Davidlohr Bueso wrote:
> From: Jason Low
>
> - Remove unnecessary head variables.
> - Delete unused parameter in queue_unlock().
>
> Cc: Ingo Molnar
> Cc: Darren Hart
> Cc: Peter Zijlstra
> Cc: Thomas Gleixner
> Cc: Mike Galbraith
> Cc: Jeff Mahoney
>
Hi Darren,
On Fri, 2013-11-22 at 21:55 -0800, Darren Hart wrote:
> On Fri, 2013-11-22 at 16:56 -0800, Davidlohr Bueso wrote:
> > We have been dealing with a customer database workload on large
> > 12Tb, 240 core 16 socket NUMA system that exhibits high amounts
> > of contention on some of the
On Fri, 2013-11-22 at 21:55 -0800, Darren Hart wrote:
> On Fri, 2013-11-22 at 16:56 -0800, Davidlohr Bueso wrote:
> > This patchset has also been tested on smaller systems for a variety of
> > benchmarks, including java workloads, kernel builds and custom
> > bang-the-hell-out-of
> > hb locks
On Fri, 2013-11-22 at 16:56 -0800, Davidlohr Bueso wrote:
> All wake_futex() callers already verify that the we are not dealing with
> a pi futex_q, so we can remove the redundant WARN() check, as this is never
> triggered anyway.
>
> Cc: Ingo Molnar
> Cc: Darren Hart
> Cc: Peter Zijlstra
>
On Thu, 21 Nov 2013, Linus Torvalds wrote:
> I do see *some* minimal comments on it from George Spelvin on lkml.
I'd like to apologize for dropping the ball on that. I started working
on it seriously, but with various emergencies, I've been AFK from lkml
for the last month.
I'm not really
From: Daniel Tang
The USB controller in TI-NSPIRE calculators are based
off either Freescale's USB OTG controller or the USB
controller found in the IMX233, both of which are
Chipidea compatible.
This patch adds a device tree binding for the controller.
Signed-off-by: Daniel Tang
---
A typo resulted in GPIO lookup failing unconditionally.
Signed-off-by: Alexandre Courbot
Reported-by: Stephen Warren
---
drivers/gpio/gpiolib.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index 980b08d..86caf17 100644
---
On Fri, 2013-11-22 at 16:56 -0800, Davidlohr Bueso wrote:
> We have been dealing with a customer database workload on large
> 12Tb, 240 core 16 socket NUMA system that exhibits high amounts
> of contention on some of the locks that serialize internal futex
> data structures. This workload
Add missing declarations and include files to avoid warnings during
compilation of include/gpio/driver.h.
Signed-off-by: Alexandre Courbot
Reported-by: Stephen Warren
---
include/linux/gpio/driver.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/gpio/driver.h
Simplify the code and fix race condition seen because
attribute files were created after hwmon device registration.
Signed-off-by: Guenter Roeck
---
Compile tested only; unfortunately I don't have the the necessary hardware.
drivers/gpu/drm/radeon/radeon_pm.c | 49
Simplify the code and resolve race conditions seen because
attribute files are created after hwmon device registration,
and removed before hwmon device removal.
Signed-off-by: Guenter Roeck
---
Compile tested only; unfortunately I don't have the the necessary hardware.
On Fri, 2013-11-22 at 21:40 -0800, Darren Hart wrote:
> On Fri, 2013-11-22 at 16:56 -0800, Davidlohr Bueso wrote:
> > In futex_wake() there is clearly no point in taking the hb->lock if
> > we know beforehand that there are no tasks to be woken. This comes
> > at the smaller cost of doing some
On Fri, 2013-11-22 at 16:56 -0800, Davidlohr Bueso wrote:
> In futex_wake() there is clearly no point in taking the hb->lock if
> we know beforehand that there are no tasks to be woken. This comes
> at the smaller cost of doing some atomic operations to keep track of
> the list's size.
On Sat, Nov 23, 2013 at 3:40 AM, Stephen Warren wrote:
> On 11/22/2013 05:14 AM, Mika Westerberg wrote:
>> From: Heikki Krogerus
>>
>> This makes it possible to request the gpio descriptors in
>> rfkill-gpio driver regardless of the platform.
>
> Patches 1-3,
> Tested-by: Stephen Warren
>
> All
On Fri, Nov 22, 2013 at 4:07 AM, Peter Zijlstra wrote:
> On Thu, Nov 21, 2013 at 09:22:24AM -0800, Yinghai Lu wrote:
>> On Thu, Nov 21, 2013 at 7:03 AM, Peter Zijlstra wrote:
>> >>
>> >> This one seems fix NULL reference in compute_group_power.
>> >>
>> >> but get following on current Linus tree
On 11/22/2013 08:25 PM, Linus Torvalds wrote:
On Fri, Nov 22, 2013 at 4:56 PM, Davidlohr Bueso wrote:
In futex_wake() there is clearly no point in taking the hb->lock if
we know beforehand that there are no tasks to be woken. This comes
at the smaller cost of doing some atomic operations to
On Fri, Nov 22, 2013 at 11:26:57AM -0800, Paul E. McKenney wrote:
> Hello!
>
> This series applies some long-needed updates to memory-barriers.txt:
>
> 1.Add ACCESS_ONCE() calls where needed to ensure their inclusion
> in code copy-and-pasted from this file.
>
> 2.Add long atomic
Vivek Goyal writes:
> On Thu, Nov 21, 2013 at 07:19:07PM +, Matthew Garrett wrote:
>> On Thu, Nov 21, 2013 at 02:13:05PM -0500, Vivek Goyal wrote:
>> > On Thu, Nov 21, 2013 at 07:06:20PM +, Matthew Garrett wrote:
>> > > That would require a certain degree of massaging from userspace if
Vivek Goyal writes:
> On Fri, Nov 22, 2013 at 05:34:03AM -0800, Eric W. Biederman wrote:
>
> [..]
>> > Why ELF case is so interesting. I have not use kexec to boot ELF
>> > images in years and have not seen others using it too. In fact bzImage
>> > seems to be the most common kernel image format
Hi Eric,
Thanks for quick reply. :-)
Also, I am confused that in v3.12 why inet_lro.c file is not found in
/net/ipv4/ directory, while Makefile has "obj-$(CONFIG_INET_LRO) +=
inet_lro.o" and LRO heads file exsits.
If I am wrong, pls correct me, :-)
See the steps 3 for details,(I have
On Fri, 2013-11-22 at 17:25 -0800, Linus Torvalds wrote:
> On Fri, Nov 22, 2013 at 4:56 PM, Davidlohr Bueso wrote:
> > In futex_wake() there is clearly no point in taking the hb->lock if
> > we know beforehand that there are no tasks to be woken. This comes
> > at the smaller cost of doing some
On Fri, Nov 22, 2013 at 5:25 PM, Linus Torvalds
wrote:
> On Fri, Nov 22, 2013 at 4:56 PM, Davidlohr Bueso wrote:
>> In futex_wake() there is clearly no point in taking the hb->lock if
>> we know beforehand that there are no tasks to be woken. This comes
>> at the smaller cost of doing some
Hi,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Friday, November 22, 2013 5:11 PM
> To: Chao Yu
> Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net; 谭姝
> Subject: Re: [f2fs-dev] [PATCH V3 2/2]
James Cloos jhcloos.com> writes:
>
> This combination:
>
> # CONFIG_SYSTEM_TRUSTED_KEYRING is not set
> CONFIG_TRUSTED_KEYS=m
>
> (acquired by oldconfig and N to system keyring)
>
> fails with:
>
> Pass 2
> CC [M] crypto/asymmetric_keys/x509_rsakey-asn1.o
> CC [M]
Hello Dan,
On Sat, Nov 23, 2013 at 6:10 AM, Dan Streetman wrote:
> Currently, zswap is writeback cache; stored pages are not sent
> to swap disk, and when zswap wants to evict old pages it must
> first write them back to swap cache/disk manually. This avoids
> swap out disk I/O up front, but
Hello Dan,
On Sat, Nov 23, 2013 at 6:10 AM, Dan Streetman wrote:
> Currently, zswap_entry_put removes the entry from its tree if
> the resulting refcount is 0. Several places in code put an
> entry's initial reference, but they also must remove the entry
> from its tree first, which makes the
--
Do you need a Loan to start or expand your business ? We give Business
Loans upto £100 million if you need funding please send sumary of your
Project to our email below: krisparker.loanage...@aim.com
Dr. Kris Parker
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
From: Randy Dunlap
Fix kernel-doc warning for duplicate definition of 'kmalloc':
Documentation/DocBook/kernel-api.xml:9483: element refentry: validity error :
ID API-kmalloc already defined
Also combine the kernel-doc info from the 2 kmalloc definitions into one
block and remove the "see
On 11/21/13 17:07, Qiang Huang wrote:
> On 2013/11/22 3:11, Randy Dunlap wrote:
>> On 11/20/13 21:57, Qiang Huang wrote:
>>>
>>> Signed-off-by: Qiang Huang
>>
>> or use my patch from 2013-09-17:
>> http://marc.info/?l=linux-mm=137944291611467=2
>>
>> Would be nice to one of these merged...
>
>
восстановите зрение без операционным способом http://glazmen.ru/
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
* Tony Lindgren [131122 17:16]:
> * Tony Lindgren [131122 17:09]:
> > * Russell King - ARM Linux [131122 16:56]:
> > > On Fri, Nov 22, 2013 at 04:43:35PM -0800, Tony Lindgren wrote:
> > > > + /* See of_device_resource_notify for populating
> > > > interrupts */
> > > > +
On Fri, Nov 22, 2013 at 07:08:16PM +0100, Alexander Graf wrote:
> Hi,
>
> With current Linus' master tree my ibook started emitting a lot of annoying
> csum calculation warnings. I've bisected it down to the commit seen in the
> subject line, but I suppose the real problem lies somewhere a lot
Hi Linus:
This is a resend with the recipients in the cc field instead of the
to field.
Here is the crypto update for 3.13:
* Made x86 ablk_helper generic for ARM.
* Phase out chainiv in favour of eseqiv (affects IPsec).
* Fixed aes-cbc IV corruption on s390.
* Added constant-time crypto_memneq
Hi Linus:
This is a resend.
Here is the crypto update for 3.13:
* Made x86 ablk_helper generic for ARM.
* Phase out chainiv in favour of eseqiv (affects IPsec).
* Fixed aes-cbc IV corruption on s390.
* Added constant-time crypto_memneq which replaces memcmp.
* Fixed aes-ctr in omap-aes.
*
Hi Linus,
Below are a number of NTB bug fixes and features for v3.13. Please
consider pulling them.
Thanks,
Jon
The following changes since commit 5e01dc7b26d9f24f39abace5da98ccbd6a5ceb52:
Linux 3.12 (2013-11-03 15:41:51 -0800)
are available in the git repository at:
On Tue, Nov 12, 2013 at 08:01:37PM +0100, Daniel Lezcano wrote:
> On 11/08/2013 10:21 PM, Soren Brinkmann wrote:
> >The currently used method adjusting the clocksource to a changing input
> >frequency does not work on kernels from 3.11 on.
> >The new approach is to keep the timer frequency as
On Fri, Nov 22, 2013 at 4:56 PM, Davidlohr Bueso wrote:
> In futex_wake() there is clearly no point in taking the hb->lock if
> we know beforehand that there are no tasks to be woken. This comes
> at the smaller cost of doing some atomic operations to keep track of
> the list's size.
Hmm. Why?
Sorry, resending due to an MUA issue.
Adding Thomas to the thread since discussion is about clocksource, and Mark
Rutland as discussion is related to timers and DT, thanks.
On 11/22/2013 02:01 PM, Rob Herring wrote:
> On Fri, Nov 22, 2013 at 10:42 AM, Joel Fernandes wrote:
>> On 11/22/2013
On Fri, 22 Nov 2013, Scott Wood wrote:
> This sounds like an incompatible change to userspace API. What about
> older glibc? What about user code that directly manipulates these bits
> rather than going through libc, or uses a libc other than glibc? Where
> is this API requirement documented?
A little late but ready and toasty warm here is iproute2 to go with
3.12.0 (aka One Giant Leap for Frogkind).
In addition to the usual build documentation fixes, this
version includes support for ipv6 on vxlan and GRE.
As well as fair queue packet scheduler.
If you have been sitting on changes
* Tony Lindgren [131122 17:09]:
> * Russell King - ARM Linux [131122 16:56]:
> > On Fri, Nov 22, 2013 at 04:43:35PM -0800, Tony Lindgren wrote:
> > > + /* See of_device_resource_notify for populating interrupts */
> > > + for (i = 0; i < num_irq; i++, res++) {
> > > +
2013/11/22 Phillip Lougher :
> On 22/11/13 21:50, Geyslan Gregório Bem wrote:
>>
>> Coverity caught double free possibility (CID 1130962).
>>
>> I can patch this, but I have to know if is correct to free comp_opts
>> in the function squashfs_decompressor_create() or it had to be done in
>> the
Adding Thomas to the thread since discussion is about clocksource, and Mark
Rutland as discussion is related to timers and DT, thanks.
On 11/22/2013 02:01 PM, Rob Herring wrote:
> On Fri, Nov 22, 2013 at 10:42 AM, Joel Fernandes wrote:
>> On 11/22/2013 09:58 AM, Rob Herring wrote:
>>> On Thu,
This combination:
# CONFIG_SYSTEM_TRUSTED_KEYRING is not set
CONFIG_TRUSTED_KEYS=m
(acquired by oldconfig and N to system keyring)
fails with:
Pass 2
CC [M] crypto/asymmetric_keys/x509_rsakey-asn1.o
CC [M] crypto/asymmetric_keys/x509_cert_parser.o
CC [M]
* Russell King - ARM Linux [131122 16:56]:
> On Fri, Nov 22, 2013 at 04:43:35PM -0800, Tony Lindgren wrote:
> > + /* See of_device_resource_notify for populating interrupts */
> > + for (i = 0; i < num_irq; i++, res++) {
> > + res->flags = IORESOURCE_IRQ;
> >
On Fri, Nov 22, 2013 at 4:43 PM, Matthew Garrett wrote:
>
> I'd sent a pull yesterday (http://lkml.org/lkml/2013/11/21/599 ) which
> may have missed your cutoff, but it seems worth checking.
No, it didn't miss my cutoff, and it wasn't even eaten by the gmail
spam filters, but it *had* missed my
* Tony Lindgren [131122 16:44]:
> @@ -168,7 +218,13 @@ struct platform_device *of_device_alloc(struct
> device_node *np,
> rc = of_address_to_resource(np, i, res);
> WARN_ON(rc);
> }
> - WARN_ON(of_irq_to_resource_table(np,
On 11/22/2013 01:36 PM, Linus Torvalds wrote:
So you had an extra week to prepare your pull requests, and if you
were planning on sending it in the last two days thinking I'd close
the merge window on Sunday as usual, I can only laugh derisively in
your general direction, and call you bad names.
All wake_futex() callers already verify that the we are not dealing with
a pi futex_q, so we can remove the redundant WARN() check, as this is never
triggered anyway.
Cc: Ingo Molnar
Cc: Darren Hart
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Mike Galbraith
Cc: Jeff Mahoney
Cc: Linus
From: Jason Low
- Remove unnecessary head variables.
- Delete unused parameter in queue_unlock().
Cc: Ingo Molnar
Cc: Darren Hart
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Mike Galbraith
Cc: Jeff Mahoney
Cc: Linus Torvalds
Cc: Scott Norton
Cc: Tom Vaden
Cc: Aswin Chandramouleeswaran
Currently, the futex global hash table suffers from it's fixed, smallish
(for today's standards) size of 256 entries, as well as its lack of NUMA
awareness. Large systems, using many futexes, can be prone to high amounts
of collisions; where these futexes hash to the same bucket and lead to
extra
From: Peter Zijlstra
Original patchset: https://lkml.org/lkml/2011/9/14/118
This is useful for locking primitives that can effect multiple
wakeups per operation and want to avoid lock internal lock contention
by delaying the wakeups until we've released the lock internal locks.
Alternatively
In futex_wake() there is clearly no point in taking the hb->lock if
we know beforehand that there are no tasks to be woken. This comes
at the smaller cost of doing some atomic operations to keep track of
the list's size. Specifically, increment the counter when an element is
added to the list, and
We have been dealing with a customer database workload on large
12Tb, 240 core 16 socket NUMA system that exhibits high amounts
of contention on some of the locks that serialize internal futex
data structures. This workload specially suffers in the wakeup
paths, where waiting on the
On Fri, Nov 22, 2013 at 04:43:35PM -0800, Tony Lindgren wrote:
> + /* See of_device_resource_notify for populating interrupts */
> + for (i = 0; i < num_irq; i++, res++) {
> + res->flags = IORESOURCE_IRQ;
> + res->start =
* Joel Fernandes [131122 16:32]:
> On 11/22/2013 11:08 AM, Tony Lindgren wrote:
> >
> > I don't think there's a dependency here to the omap clocks as the dmtimer
> > can implement the clocksource separately and internally still use clk_get
> > using the clock alias table.
>
> You mean implement
The mm-of-the-moment snapshot 2013-11-22-16-50 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
Hi Linus,
I'd sent a pull yesterday (http://lkml.org/lkml/2013/11/21/599 ) which
may have missed your cutoff, but it seems worth checking.
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Currently we get the following kind of errors if we try to use
interrupt phandles to irqchips that have not yet initialized:
irq: no irq domain found for /ocp/pinmux@48002030 !
WARNING: CPU: 0 PID: 1 at drivers/of/platform.c:171
of_device_alloc+0x144/0x184()
Modules linked in:
CPU: 0 PID: 1
On 11/22/2013 11:08 AM, Tony Lindgren wrote:
> * Joel Fernandes [131122 08:37]:
>> Hi Tony,
>>
>> Thanks for your comments, few replies inline below..
>>
>> On 11/22/2013 09:58 AM, Tony Lindgren wrote:
>>> * Joel Fernandes [131121 18:00]:
+Required properties for system timers
On Fri, Nov 22, 2013 at 11:05:24PM +, Mel Gorman wrote:
> On Fri, Nov 22, 2013 at 03:28:07PM -0600, Alex Thorlton wrote:
> > > If the warning added by that patch does *not* trigger than can you also
> > > test this patch? It removes the barriers which should not be necessary
> > > and takes a
On Fri, Nov 22, 2013 at 10:11:56PM +0100, Jan Kara wrote:
> Hi,
>
> On Wed 13-11-13 16:11:47, Dave Jones wrote:
> > here's another one..
> >
> >
> > =
> > [ INFO: possible recursive locking detected ]
> > 3.12.0+ #2 Not tainted
> >
On Fri, 2013-11-22 at 15:57 +0100, Jonas Jensen wrote:
> The kernel now has a MDIO bus driver and a phy_driver (RTL8201CP),
> connect to this PHY using OF and add ethtool support.
>
> Signed-off-by: Jonas Jensen
> ---
>
> Notes:
> Applies to next-20131122
>
&
On Wed, 06 Nov 2013 19:05:57 +0400 Maxim Patlasov
wrote:
> "strictlimit" feature was introduced to enforce per-bdi dirty limits for
> FUSE which sets bdi max_ratio to 1% by default:
>
> http://article.gmane.org/gmane.linux.kernel.mm/105809
>
> However the feature can be useful for other
On Fri, 22 Nov 2013 14:30:47 -0800
Andrew Morton wrote:
> On Fri, 22 Nov 2013 12:01:06 -0500 Luiz Capitulino
> wrote:
>
> > Signed-off-by: Luiz capitulino
> > ---
> > include/linux/mmzone.h | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git
From: Lv Zheng
As there is only CONFIG_ACPI=n processing in the , it is not
safe to include , and
directly for source out of Linux ACPI subsystems.
This patch adds error messaging to warn developers of such wrong
inclusions.
In order not to be bisected and reverted as a wrong commit, warning
From: Lv Zheng
This patch cleans up inclusions.
1. For files where is already included, this patch cleans up
them by deleting inclusions. Note that if
is included before including in the original file, the
inclusion of is moved up to avoid issues from happening.
2. The sfi_acpi
From: Lv Zheng
This patch enfoces inclusion instead of direct
and inclusions.
It's required that included prior than
to find declarations for acpi_pci_root.
It is required that included prior than
to find declarations for acpi_handle and acpi_notify_handler.
In order to work around
From: Lv Zheng
The header file is the top level header for other kernel
subsystems to include. It contains environemnt settings and architecture
specific implementation that should be included before including other
ACPICA headers in order to keep a consistent build environment for ACPICA
From: Lv Zheng
ACPICA header files are lacking in stub protections. This makes all ACPICA
header files could only be included for CONFIG_ACPI=y environment. This
infects new ACPI prototypes, if such prototypes referenced ACPICA defined
types, they must be incldued only in the CONFIG_ACPI=y
On Fri, 8 Nov 2013 11:21:13 +0100 Jan Kara wrote:
> On Fri 08-11-13 00:46:49, Frederic Weisbecker wrote:
> > On Thu, Nov 07, 2013 at 06:37:17PM -0500, Steven Rostedt wrote:
> > > On Fri, 8 Nov 2013 00:21:51 +0100
> > > Frederic Weisbecker wrote:
> > > >
> > > > Offloading to a workqueue would
On 22/11/13 21:50, Geyslan Gregório Bem wrote:
Coverity caught double free possibility (CID 1130962).
I can patch this, but I have to know if is correct to free comp_opts
in the function squashfs_decompressor_create() or it had to be done in
the caller. My bet is the caller.
128void
On Fri, 2013-11-22 at 12:20 +0400, Vladimir Davydov wrote:
> On e1000_down(), we should ensure every asynchronous work is canceled
> before proceeding. Since the watchdog_task can schedule other works
> apart from itself, it should be stopped first, but currently it is
> stopped after the
On Thu, Nov 14, 2013 at 6:56 AM, Oleg Nesterov wrote:
> Move the setting of PF_NO_SETAFFINITY up before set_cpus_allowed()
> in create_worker(). Otherwise userland can change ->cpus_allowed
> in between.
>
> Signed-off-by: Oleg Nesterov
Applied to wq/for-3.13-fixes.
Thanks!
--
tejun
--
To
On Fri, 2013-11-22 at 12:20 +0400, Vladimir Davydov wrote:
> The patch fixes the following lockdep warning, which is 100%
> reproducible on network restart:
>
> ==
> [ INFO: possible circular locking dependency detected ]
> 3.12.0+ #47 Tainted:
On Saturday, November 23, 2013 12:22:23 AM Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Rework acpi_bus_trim() and acpi_bus_device_attach(), which is
> renamed as acpi_bus_attach(), to walk the list of each device
> object's children directly and call themselves recursively for
> each
From: Rafael J. Wysocki
Rework acpi_bus_trim() and acpi_bus_device_attach(), which is
renamed as acpi_bus_attach(), to walk the list of each device
object's children directly and call themselves recursively for
each child instead of using acpi_walk_namespace(). This
simplifies the code quite a
On Fri, Nov 22, 2013 at 03:28:07PM -0600, Alex Thorlton wrote:
> > If the warning added by that patch does *not* trigger than can you also
> > test this patch? It removes the barriers which should not be necessary
> > and takes a reference tot he page before waiting on the lock. The
> > previous
On Thu, Nov 21, 2013 at 11:54 PM, yzhu1 wrote:
> Hi, maintainers
>
> This change is based on a similar change made to e1000e support in
> commit bb9e44d0d0f4 ("e1000e: prevent oops when adapter is being closed
> and reset simultaneously"). The same issue has also been observed
> on the older
Hello,
On Wed, Nov 20, 2013 at 12:51:21AM -0500, Tejun Heo wrote:
> The patch is just extremely marginal. Ah well... why not? I'll apply
> it once -rc1 drops.
So, I was about to apply this patch but decided against it. It
doesn't really make anything better and the code looks worse
On Fri, 8 Nov 2013 20:47:38 +0800 Zhi Yong Wu wrote:
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -611,7 +611,7 @@ static int me_pagecache_clean(struct page *p, unsigned
> long pfn)
> }
>
> /*
> - * Dirty cache page page
> + * Dirty cache page
> * Issues: when the error
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive 2nd round of updates for the input subsystem. You will get a
new driver for Surface
This commit enables the watchdog driver for the BCM281xx family of SoCs.
Signed-off-by: Markus Mayer
Reviewed-by: Matt Porter
Acked-by: Guenter Roeck
---
arch/arm/configs/bcm_defconfig |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/configs/bcm_defconfig
This is version 5 of the watchdog driver for the BCM281xx family of mobile
SoCs.
Changes since version 4:
- Fixed whitespace issue in Kconfig "help" section
- Rebased onto 3.13-rc1 (due to merge conflict in Makefile)
Changes since version 3:
- Removed #include
- Added Reviewed-by:/Acked-by:
This commit adds support for the watchdog timer used on the BCM281xx
family of SoCs.
Signed-off-by: Markus Mayer
Reviewed-by: Matt Porter
Reviewed-by: Guenter Roeck
---
drivers/watchdog/Kconfig| 22 +++
drivers/watchdog/Makefile |1 +
drivers/watchdog/bcm_kona_wdt.c | 365
Hi Tejun,
On Fri, Nov 22, 2013 at 11:18 PM, Tejun Heo wrote:
> Just applied to cgroup/for-3.13-fixes w/ stable cc'd. Will push to
> Linus next week.
Thank your for your quick reply. Do you also have a backport for
v3.10.x already available?
Best regards,
--
William
--
To unsubscribe from
On Fri, Nov 22, 2013 at 02:47:38PM -0800, Dmitry Torokhov wrote:
> On Sat, Mar 16, 2013 at 09:21:40AM -0700, Greg Kroah-Hartman wrote:
> > On Thu, Mar 14, 2013 at 08:24:45PM -0700, Guenter Roeck wrote:
> > > Provide devres functions for device_create_file, sysfs_create_file,
> > > and
On 11/22/2013 02:24 PM, Chang wrote:
>
> On 11/22/2013 03:27 PM, Vlad Yasevich wrote:
>> On 11/22/2013 02:49 AM, Chang Xiangzhong wrote:
>>> tsn_gap_acked is an important state flag in chunk, which indicates if
>>> the
>>> chunk has been acked in gap reports before.
>> Actually, this bit
On Fri, Nov 22, 2013 at 5:45 PM, Joe Perches wrote:
> On Fri, 2013-11-22 at 17:17 -0500, Elena Ufimtseva wrote:
>> Based on Richard Weinberger patch https://lkml.org/lkml/2012/3/16/510
>> Functions like this one are evil:
>>
>> void foo()
>> {
>> ...
>> }
> []
>> - added white space in
On Sat, Mar 16, 2013 at 09:21:40AM -0700, Greg Kroah-Hartman wrote:
> On Thu, Mar 14, 2013 at 08:24:45PM -0700, Guenter Roeck wrote:
> > Provide devres functions for device_create_file, sysfs_create_file,
> > and sysfs_create_group plus the respective remove functions.
> >
> > Idea is to be able
On Fri, 2013-11-22 at 17:17 -0500, Elena Ufimtseva wrote:
> Based on Richard Weinberger patch https://lkml.org/lkml/2012/3/16/510
> Functions like this one are evil:
>
> void foo()
> {
> ...
> }
[]
> - added white space in regular expression between (), based
> on comments from Joe Perches.
On Mon, 2013-11-04 at 16:52 +, Joseph S. Myers wrote:
> From: Joseph Myers
>
> The e500 SPE floating-point emulation code clears existing exceptions
> (__FPU_FPSCR &= ~FP_EX_MASK;) before ORing in the exceptions from the
> emulated operation. However, these exception bits are the "sticky",
On Thu, 2013-11-21 at 14:17 +0800, dyo...@redhat.com wrote:
> Hi,
>
> Here is the V3 for supporting kexec kernel efi runtime.
> Per pervious discussion I pass the 1st kernel efi runtime mapping
> via setup_data to 2nd kernel. Besides of the runtime mapping
> info I also pass the fw_vendor,
On Mon, 18 Nov 2013, Viresh Kumar wrote:
> On Fri, Mar 22, 2013 at 3:23 AM, Thomas Gleixner wrote:
> > --- linux-2.6.orig/kernel/cpu/idle.c
> > +++ linux-2.6/kernel/cpu/idle.c
>
> > +void cpu_startup_entry(enum cpuhp_state state)
> > +{
> > + current_set_polling();
> > +
On Friday, November 22, 2013 08:43:55 AM Bjorn Helgaas wrote:
> [+cc Rafael, James]
>
> On Tue, Nov 19, 2013 at 11:18 PM, Tejun Heo wrote:
> > (cc'ing Bjorn)
> >
> > Hello,
> >
> > On Tue, Nov 19, 2013 at 03:09:58PM +0200, Mika Westerberg wrote:
> >> Commit bcdde7e221a8 (sysfs: make
On Fri, 22 Nov 2013 12:01:06 -0500 Luiz Capitulino
wrote:
> Signed-off-by: Luiz capitulino
> ---
> include/linux/mmzone.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
> index bd791e4..5e202d6 100644
> ---
On Fri, 22 Nov 2013, Rafael J. Wysocki wrote:
> On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
> > Ok, I've finally managed to find out the bad commit:
> > ad07277e82dedabacc52c82746633680a3187d25: ACPI / PM: Hold acpi_scan_lock
> > over system PM transitions
> >
> > I verified
1 - 100 of 1074 matches
Mail list logo
