2013/2/2 Michael Kerrisk (man-pages) :
>
> On Jan 30, 2013 8:05 AM, "Andrey Vagin" wrote:
>>
>> If signalfd is created with the flag SFD_PEEK, it reads siginfo-s
>> without dequeuing signals.
>>
>> For reading not first siginfo pread(fd, buf, size, pos) can be used,
>> where ppos / sizeof(signalfd
On Saturday 02 February 2013 02:31 AM, Matt Porter wrote:
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter
Acked-by: Tony Lindgren
---
Acked-by: Santosh Shilimkar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Saturday 02 February 2013 02:31 AM, Matt Porter wrote:
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports platforms booting
with or without DT populated.
Signed-off-by: Matt Porter
Acked-by: Tony Lindgren
---
Acked-by: Santosh Shilimkar
--
To unsub
(forgot to cc Kirill A. Shutemov , added)
On 2013/2/2 14:50, Li Zefan wrote:
> There're three bugs.
>
> - If thread A is removing a cgroup, while thread B is closing an eventfd, the
> two threads might free the same cgroup event and thus crash the kernel.
>
> This is fixed by patch #1 and patch
If read() returns with errno == EIDRM, we know the cgroup has been
removed.
Signed-off-by: Li Zefan
---
tools/cgroup/cgroup_event_listener.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/tools/cgroup/cgroup_event_listener.c
b/tools/cgroup/cgroup_event_listener
Currently when a cgroup is removed, it calls eventfd_signal() for
each registered cgroup event, so userspace can be notified and blocked
reads can be unblocked.
The problem is, if we have multiple threads blocked on the same eventfd,
only one of them will be unlocked.
This patch makes sure all op
There're three bugs.
- If thread A is removing a cgroup, while thread B is closing an eventfd, the
two threads might free the same cgroup event and thus crash the kernel.
This is fixed by patch #1 and patch #2.
- If there're multiple threads are blocking in read() on the same eventfd,
and someon
commit 205a872bd6f9a9a09ef035ef1e90185a8245cc58 ("cgroup: fix lockdep
warning for event_control") sovled a deadlock by introducing a new
bug.
We can't access @event without event_list_lock, otherwise we'll race
with cgroup_event_wake() called when closing the eventfd, and then
both threads will tr
When an eventfd is closed, a wakeup with POLLHUP will be issued,
but cgroup wants to issue wakeup explicitly, so when a cgroup is
removed userspace can be notified.
Signed-off-by: Li Zefan
---
fs/eventfd.c| 11 +++
include/linux/eventfd.h | 5 +
2 files changed, 16 inser
Hi. Jan.
Sorry for interrupt.
Have you taken this patch to your tree ? I can not find it..
or Is there any issue regarding this patch ?
Thanks!
2013/1/22, Namjae Jeon :
> 2013/1/22, Jan Kara :
>> On Tue 22-01-13 09:45:09, Namjae Jeon wrote:
>>> 2013/1/21, Jan Kara :
>>> > @@ -,6 +2219,8 @@ i
On Fri, Feb 1, 2013 at 10:51 PM, Joerg Roedel wrote:
> Cho,
>
> On Wed, Jan 02, 2013 at 02:53:49PM +0900, KyongHo Cho wrote:
>> On Tuesday, January 1, 2013, Sylwester Nawrocki
>>
>
>> > Cc: devicetree-disc...@lists.ozlabs.org
>
> Since patch 7 of this set is already merged, do you mind to re-pos
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
arch/x86/mm/numa.c: In function 'setup_node_data':
arch/x86/mm/numa.c:222:3: warning: passing argument 1 of '__phys_addr_nodebug'
makes integer from pointer without a cast [enabled by defaul
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
arch/x86/kernel/kvm.c: At top level:
arch/x86/kernel/kvm.c:509:2: warning: initialization from incompatible pointer
type [enabled by default]
arch/x86/kernel/kvm.c:509:2: warning: (near init
On 2 February 2013 11:14, Dirk Brandewie wrote:
> Hi viresh,
>
> This is based on 3.8-rc5. I think this should work against bleeding_edge
> but I have not tested against bleeding_edge
Rafael wouldn't be able to apply these patches. There are a lot of core patches
present in bleeding_edge.
--
To
Hi all,
Today's linux-next merge of the kvm tree got a conflict in
arch/x86/include/asm/vmx.h between commit af170c5061dd ("UAPI: (Scripted)
Disintegrate arch/x86/include/asm") from Linus' tree and commits
83d4c286931c ("x86, apicv: add APICv register virtualization support")
and c7c9c56ca26f ("x8
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
arch/x86/kernel/kvm.c: In function 'kvm_register_steal_time':
arch/x86/kernel/kvm.c:302:3: warning: format '%lx' expects argument of type
'long unsigned int', but argument 3 has type 'phys_a
On Sat, Feb 2, 2013 at 12:15 AM, wrote:
> From: Dirk Brandewie
>
> There is an additional reference added to the driver in
> cpufreq_add_dev_policy() that is removed in__cpufreq_governor() if the
> driver implements target(). Remove the last reference when the driver
> implements setpolicy()
>
On Sat, Feb 2, 2013 at 12:15 AM, wrote:
> From: Dirk Brandewie
>
> Scaling drivers that implement internal governors do not have governor
> sturctures associated with them. Do not create/remove statisitcs
> entries for polices that do not have governors associated with them.
>
> Signed-off-by:
Hi all,
After merging the tip tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/perf/power7-pmu.c:397:2: error: initialization from incompatible
pointer type [-Werror]
arch/powerpc/perf/power7-pmu.c:397:2: error: (near initialization for
'power7_events_attr
The return statement after BUG() is invalid, move BUG() to the default choice
of the switch.
Signed-off-by: Jie Liu
---
kernel/res_counter.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/kernel/res_counter.c b/kernel/res_counter.c
index ff55247..748a3bc 100644
---
Shaohua,
In next-20130128, commit 174f064 "swap: make each swap partition have
one address_space" (from the mm/akpm tree) appears causes a hang/RCU
stall for me when hot-unplugging a CPU.
I'm running on a quad-core ARM system, and hot-unplugging a CPU using:
echo 0 > /sys/devices/system/cpu/cpu2
2013/2/2 anish kumar :
> On Sat, 2013-01-26 at 17:24 +0100, Frederic Weisbecker wrote:
>> 2012/11/3 anish kumar :
>> > From: anish kumar
>> >
>> > As no one is using the return value of irq_work_queue function
>> > it is better to just make it void.
>> >
>> > Acked-by: Steven Rostedt
>> > Signed-
Hi Artem,
After merging the l2-mtd tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
In file included from drivers/mtd/chips/cfi_cmdset_0002.c:36:0:
include/linux/of_platform.h:107:13: warning: 'struct of_device_id' declared
inside parameter list [enabled by default]
On Sat, Dec 01, 2012 at 11:33:41PM +, Cong Ding wrote:
> it is unnecessary to check i<4 after the loop. just do it before the break.
>
> Signed-off-by: Cong Ding
Thanks, applied.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux
On Sat, Feb 2, 2013 at 12:15 AM, wrote:
> From: Dirk Brandewie
>
> Scaling drivers that implement internal governors do not have governor
> structures assocaited with them. Only track the name of the governor
> associated with the CPU if the driver does not implement
> cpufreq_driver.setpolicy(
On Sat, Feb 2, 2013 at 12:15 AM, wrote:
> From: Dirk Brandewie
>
> Scaling drivers that implement cpufreq_driver.setpolicy() have
> internal governors and may/will change the current operating frequency
> very frequently this will cause cpufreq_out_of_sync() to be called
> every time. Only call
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
drivers/net/vmxnet3/vmxnet3_drv.c between commit 6cdd20c380eb ("vmxnet3:
set carrier state properly on probe") from the net tree and commit
204a6e659439 ("vmxnet3: use netdev_ printk wrappers") from the net-next
tree.
I fixed
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
net/ipv6/route.c between commit bd30e947207e ("ipv6: do not create
neighbor entries for local delivery") from the net tree and commit
c440f1609b65 ("ipv6: Do not depend on rt->n in ip6_pol_route()") from the
net-next tree.
I
On Fri, 2013-02-01 at 09:59 -0500, Don Zickus wrote:
> On Fri, Feb 01, 2013 at 07:19:07PM +0530, anish kumar wrote:
> > From: anish kumar
> >
> > This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
> > multifold.
> > Uses are:
> > 1. Check if smpboot_register_percpu_thread
On Sat, 2013-01-26 at 17:24 +0100, Frederic Weisbecker wrote:
> 2012/11/3 anish kumar :
> > From: anish kumar
> >
> > As no one is using the return value of irq_work_queue function
> > it is better to just make it void.
> >
> > Acked-by: Steven Rostedt
> > Signed-off-by: anish kumar
> > ---
> >
On Sat, Feb 2, 2013 at 12:19 AM, wrote:
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> @@ -1219,6 +1219,9 @@ unsigned int cpufreq_quick_get(unsigned int cpu)
> struct cpufreq_policy *policy = cpufreq_cpu_get(cpu);
> unsigned int ret_freq = 0;
>
> + i
End user documentation is on our github. I think it should go with the user
level utilities, rather than the kernel driver.
-Amit
> -Original Message-
> From: Kent Overstreet [mailto:koverstr...@google.com]
> Sent: Friday, February 01, 2013 5:25 PM
> To: Michel Lespinasse
> Cc: Darrick J.
On 2013/2/2 7:06, Bjorn Helgaas wrote:
> On Wed, Jan 30, 2013 at 9:10 AM, Jiang Liu wrote:
>> From: Jiang Liu
>>
>> With commit 4f535093cf8f6da8c "PCI: Put pci_dev in device tree as
>> early as possible", companion ACPI devices should be created before
>> creating correspoding PCI devices, otherw
>> intel_idle already uses a driver-specific flag:
>>
>> #define CPUIDLE_FLAG_TLB_FLUSHED0x1
>>
>> This patch just uses 4 more bits along with that one.
>
> Ok. In this case it would make sense to move this flag out of the
> generic core code to the intel_idle.c file ?
This flag is a
Hello.
On 02-02-2013 4:44, Russell King - ARM Linux wrote:
On Fri, Feb 01, 2013 at 11:49:11PM +0300, Sergei Shtylyov wrote:
good point, do you wanna send some patches ?
I have already sent them countless times and even stuck CPPI 4.1 support
(in
arch/arm/common/cppi41.c) in Russell's
Hi,
After merging the nfsd tree, today's linux-next build (x86_64
allmodconfig) failed like this:
fs/nfs/dns_resolve.c: In function 'nfs_dns_resolver_cache_init':
fs/nfs/dns_resolve.c:375:4: error: 'struct cache_detail' has no member named
'cache_upcall'
fs/nfs/dns_resolve.c:375:35: warning: lef
From: Andi Kleen
Add support for the v2 PEBS format. It has a superset of the v1 PEBS
fields, but has a longer record so we need to adjust the code paths.
The main advantage is the new "EventingRip" support which directly
gives the instruction, not off-by-one instruction. So with precise == 2
we
From: Andi Kleen
Recent Intel CPUs have a new alternative MSR range for perfctrs that allows
writing the full counter width. Enable this range if the hardware reports it
using a new capability bit. This lowers overhead of perf stat slightly because
it has to do less interrupts to accumulate the c
From: Andi Kleen
Add basic PEBS support for Haswell.
The constraints are similar to SandyBridge with a few new events.
v2: Readd missing pebs_aliases
v3: Readd missing hunk. Fix some constraints.
v4: Fix typo in PEBS event table (Stephane Eranian)
Reviewed-by: Stephane Eranian
Signed-off-by: An
From: Andi Kleen
Add basic Haswell PMU support.
Similar to SandyBridge, but has a few new events and two
new counter bits.
There are some new counter flags that need to be prevented
from being set on fixed counters, and allowed to be set
for generic counters.
Also we add support for the counte
This is based on v7 of the full Haswell PMU support, but
ported to the latest perf/core and stripped down to the
extreme "perf for dummies" edition as requested.
I removed some more patches, these will come soon later.
I moved parts of an later patch (counter constraints for qualifiers)
into a
From: Andi Kleen
This avoids some problems with spurious PMIs on Haswell.
Haswell seems to behave more like P4 in this regard. Do
the same thing as the P4 perf handler by unmasking
the NMI only at the end. Shouldn't make any difference
for earlier non P4 cores.
Signed-off-by: Andi Kleen
---
ar
On Fri, Feb 01, 2013 at 05:25:29PM -0800, Kent Overstreet wrote:
> Also, where's the end user documentation?
I was trying not to explode this patch's size, since the doc can go straight
into Documentation/ without as much fuss as, say, the ~1600 checkpatch
warnings and all the other comments we'll
> And there's a patchset [1] from Jiri to support some kind of formula -
> yeah, now I've written the correct spelling. :) - that might fit to this
> purpose if you provide suitable formula file IMHO. So I guess we don't
> need to have another command and can reuse perf stat, no?
Yes with a prope
Also, where's the end user documentation?
On Fri, Feb 1, 2013 at 5:23 PM, Kent Overstreet wrote:
> On Fri, Feb 1, 2013 at 4:57 PM, Michel Lespinasse wrote:
>> On Fri, Feb 1, 2013 at 4:44 PM, Darrick J. Wong
>> wrote:
>>> This is a patch to migrate STEC's enhanceio driver out of their github
>>
On Fri, Feb 1, 2013 at 4:57 PM, Michel Lespinasse wrote:
> On Fri, Feb 1, 2013 at 4:44 PM, Darrick J. Wong
> wrote:
>> This is a patch to migrate STEC's enhanceio driver out of their github
>> repository and into the staging tree. From their README:
>>
>> "EnhanceIO driver is based on EnhanceIO
On Sat, Nov 03, 2012 at 11:58:30AM +0100, Julia Lawall wrote:
> From: Julia Lawall
>
> Use WARN rather than printk followed by WARN_ON(1), for conciseness.
>
> A simplified version of the semantic patch that makes this transformation
> is as follows: (http://coccinelle.lip6.fr/)
>
> //
> @@
>
On Fri, Feb 1, 2013 at 4:44 PM, Darrick J. Wong wrote:
> This is a patch to migrate STEC's enhanceio driver out of their github
> repository and into the staging tree. From their README:
>
> "EnhanceIO driver is based on EnhanceIO SSD caching software product developed
> by STEC Inc. EnhanceIO wa
On Sat, Feb 02, 2013 at 04:07:59AM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 02-02-2013 1:30, Russell King - ARM Linux wrote:
>
>>> On Fri, Feb 01, 2013 at 11:49:11PM +0300, Sergei Shtylyov wrote:
> good point, do you wanna send some patches ?
>
I have already sent them countless t
On Thu, 17 Jan 2013 14:52:52 -0800
Cody P Schafer wrote:
> Summaries:
> 1 - avoid repeating checks for section in page flags by adding a define.
> 2 - add & switch to zone_end_pfn() and zone_spans_pfn()
> 3 - adds zone_is_initialized() & zone_is_empty()
> 4 - adds a VM_BUG using zone_is_initializ
On Fri, 1 Feb 2013 16:28:48 -0800
Andrew Morton wrote:
> > + if (ret)
> > + pr_debug("page %lu outside zone [ %lu - %lu ]\n",
> > + pfn, start_pfn, start_pfn + sp);
> > +
> > return ret;
> > }
>
> As this condition leads to a VM_BUG_ON(), "pr_debug" seems rathe
On Thu, 17 Jan 2013 14:52:58 -0800
Cody P Schafer wrote:
> Add a debug message which prints when a page is found outside of the
> boundaries of the zone it should belong to. Format is:
> "page $pfn outside zone [ $start_pfn - $end_pfn ]"
>
> Signed-off-by: Cody P Schafer
> ---
> mm/page_
On Thu, 17 Jan 2013 14:52:57 -0800
Cody P Schafer wrote:
> From: Cody P Schafer
>
> Add pgdat_end_pfn() and pgdat_is_empty() helpers which match the similar
> zone_*() functions.
>
> Change node_end_pfn() to be a wrapper of pgdat_end_pfn().
>
> ...
>
> --- a/include/linux/mmzone.h
> +++ b/inc
On Thu, 17 Jan 2013 14:52:53 -0800
Cody P Schafer wrote:
> Instead of directly utilizing a combination of config options to determine
> this,
> add a macro to specifically address it.
>
> ...
>
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -625,6 +625,10 @@ static inline pte_t mayb
Hello.
On 02-02-2013 1:30, Russell King - ARM Linux wrote:
On Fri, Feb 01, 2013 at 11:49:11PM +0300, Sergei Shtylyov wrote:
good point, do you wanna send some patches ?
I have already sent them countless times and even stuck CPPI 4.1 support (in
arch/arm/common/cppi41.c) in Russell's pa
On Wed, 30 Jan 2013 16:26:19 -0800
Michel Lespinasse wrote:
> This change adds a page_mask argument to follow_page.
>
> follow_page sets *page_mask to HPAGE_PMD_NR - 1 when it encounters a THP page,
> and to 0 in other cases.
>
> __get_user_pages() makes use of this in order to accelerate popul
Hello.
On 02-02-2013 1:30, Russell King - ARM Linux wrote:
On Fri, Feb 01, 2013 at 11:49:11PM +0300, Sergei Shtylyov wrote:
good point, do you wanna send some patches ?
I have already sent them countless times and even stuck CPPI 4.1 support (in
arch/arm/common/cppi41.c) in Russell's pa
Hello.
On 01-02-2013 22:59, Matt Porter wrote:
Move mach-davinci/dma.c to common/edma.c so it can be used
by OMAP (specifically AM33xx) as well.
I think this should rather go to drivers/dma/?
No, this is the private EDMA API. It's the analogous thing to
the private OMAP dma API that is in
On Fri, Feb 1, 2013 at 12:50 AM, Yijing Wang wrote:
> On 2013/1/31 23:59, Yinghai Lu wrote:
>> On Thu, Jan 31, 2013 at 7:37 AM, Jiang Liu wrote:
>>>
>>> So I think the code in handle_hotplug_event_bridge() to handle P2P
>>> hot-addition
>>> is dead. Yijing has helped to test the code by faking A
On Fri, 1 Feb 2013 14:00:58 -0800
Mukesh Rathor wrote:
> On Thu, 31 Jan 2013 18:44:46 -0800
> Mukesh Rathor wrote:
>
> > On Thu, 31 Jan 2013 18:30:15 -0800
> > Mukesh Rathor wrote:
> >
> > > This patch fixes a fixme in Linux to use
> > > alloc_xenballooned_pages() to allocate pfns for grant t
On Fri, Feb 1, 2013 at 3:49 AM, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 3.4.29 release.
> There are 33 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Resp
On Fri, Feb 1, 2013 at 6:07 AM, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 3.7.6 release.
> There are 89 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Respo
On Fri, 2013-02-01 at 23:21 +0100, Rafael J. Wysocki wrote:
> On Friday, February 01, 2013 01:40:10 PM Toshi Kani wrote:
> > On Fri, 2013-02-01 at 07:30 +, Greg KH wrote:
> > > On Thu, Jan 31, 2013 at 06:32:18PM -0700, Toshi Kani wrote:
> > > > This is already done for PCI host bridges and pla
On Wed, Jan 30, 2013 at 9:10 AM, Jiang Liu wrote:
> From: Jiang Liu
>
> Commit 668192b678201d2fff27c "PCI: acpiphp: Move host bridge hotplug
> to pci_root.c" has moved PCI host bridge hotplug logic from acpiphp
> to pci_root, but there is still PCI host bridge hotplug related
> dead code left in
On Fri, Feb 1, 2013 at 4:06 PM, Bjorn Helgaas wrote:
> On Wed, Jan 30, 2013 at 9:10 AM, Jiang Liu wrote:
>> From: Jiang Liu
>>
>> With commit 4f535093cf8f6da8c "PCI: Put pci_dev in device tree as
>> early as possible", companion ACPI devices should be created before
>> creating correspoding PCI
On Fri, 1 Feb 2013 11:43:36 +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.
>
Hello.
On 02-02-2013 0:56, Felipe Balbi wrote:
good point, do you wanna send some patches ?
I have already sent them countless times and even stuck CPPI 4.1 support (in
arch/arm/common/cppi41.c) in Russell's patch system. TI requested to remove the
patch. :-(
sticking into arch/arm/co
Thomas,
The PREEMPT_RT behavior of moving pagefault_disable() and
pagefault_enable() into mm/memory.c as EXPORT_SYMBOL_GPL symbols breaks
compilation of a third-party driver that builds fine on a stock kernel.
Yes, I know, I know, it's a binary driver, but my problem is that it
already compiles an
On Wed, Jan 30, 2013 at 9:10 AM, Jiang Liu wrote:
> From: Jiang Liu
>
> With commit 4f535093cf8f6da8c "PCI: Put pci_dev in device tree as
> early as possible", companion ACPI devices should be created before
> creating correspoding PCI devices, otherwise it will break the ACPI
> PCI binding logic
On Fri, Feb 01, 2013 at 04:38:42PM -0600, Kent Yoder wrote:
> >> > https://github.com/shpedoikal/linux.git tpmdd-01-22-13
> >>
> >> Thanks Kent, I will try to test your branch next week, if I am able.
> >>
> >> Can you also grab
> >>
> >> https://github.com/jgunthorpe/linux/commit/98b2a198b43b41b0
On 1 February 2013 21:09, Peter Hurley wrote:
> Hi Mark,
>
> I think what Alan means is that the suspend/resume code should just
> mask/unmask interrupts at the OHCI controller, via the OHCI
> IntEventClear/Set registers (naturally, saving the current mask and
> restoring it on resume).
>
> Of cou
On Thu, Jan 31, 2013 at 11:35 AM, Paul Bolle wrote:
> In each suspend and resume cycle my laptop prints these messages at
> KERN_INFO level:
> pciehp :00:1c.1:pcie04: pciehp_suspend ENTRY
> pciehp :00:1c.0:pcie04: pciehp_suspend ENTRY
>
> and
> pciehp :00:1c.0:pcie04: pcieh
Current kernels print this on my Dell server:
[ cut here ]
WARNING: at drivers/iommu/intel_irq_remapping.c:542
intel_enable_irq_remapping+0x7b/0x27e()
Hardware name: PowerEdge R620
Your BIOS is broken and requested that x2apic be disabled
This will leave y
Quoting Prashant Gaikwad (2013-01-31 20:49:47)
> On Friday 25 January 2013 10:14 AM, Stephen Warren wrote:
> > On 01/24/2013 04:57 PM, Mike Turquette wrote:
> >> Quoting Stephen Warren (2013-01-24 11:32:37)
> >>> On 01/24/2013 11:20 AM, Mike Turquette wrote:
> Quoting Prashant Gaikwad (2013-01
On 01/17/2013 01:56 PM, Alan Stern wrote:
On Thu, 17 Jan 2013, Joseph Salisbury wrote:
Hello,
Please consider reverting commit
3d037774b42ed677f699b1dce7d548d55f4e4c2b in mainline as well as in the
current stable releases. It was included upstream as of v3.6-rc6. This
commit introduced a reg
On Fri, Feb 1, 2013 at 9:13 AM, Jiang Liu wrote:
> On 01/29/2013 10:04 AM, Jiang Liu wrote:
>> On 2013-1-29 8:34, Rafael J. Wysocki wrote:
>>> On Monday, January 28, 2013 01:56:33 PM Bjorn Helgaas wrote:
On Fri, Jan 18, 2013 at 9:07 AM, Jiang Liu wrote:
> This is an RFC patchset to addre
On Fri, 1 Feb 2013 20:23:12 +0800
Ming Lei wrote:
> Currently, sizeof(struct parsed_partitions) may be 64KB in 32bit arch,
> so it is easy to trigger page allocation failure by check_partition,
> especially in hotplug block device situation(such as, USB mass storage,
> MMC card, ...), and Felipe
On Mon, Jan 28, 2013 at 8:11 AM, Kent Yoder wrote:
> On Fri, Jan 25, 2013 at 01:25:38PM -0700, Jason Gunthorpe wrote:
>> On Tue, Jan 22, 2013 at 05:29:23PM -0600, Kent Yoder wrote:
>> > Hi Jason,
>> >
>> > On Wed, Nov 21, 2012 at 3:15 PM, Jason Gunthorpe
>> > wrote:
>> > > We've been testing an a
Hi Prabhakar,
On 01/29/2013 02:07 PM, Prabhakar Lad wrote:
[...]
diff --git a/Documentation/devicetree/bindings/media/i2c/tvp514x.txt
b/Documentation/devicetree/bindings/media/i2c/tvp514x.txt
new file mode 100644
index 000..55d3ffd
--- /dev/null
+++ b/Documentation/devicetree/bindings/media
Add support for the Acer C7's trackpad, which is a reuse
of the Samsung Series 5 550 trackpad.
Signed-off-by: Benson Leung
---
drivers/platform/x86/chromeos_laptop.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/platform/x86/chromeos_laptop.c
b/drivers/platform/x86/chromeos
The Samsung Series 5 Chromebook is equipped with a Taos tsl2583
light sensor. Instatiate it here.
Signed-off-by: Benson Leung
---
drivers/platform/x86/chromeos_laptop.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/drivers/platform/x86/chromeos_laptop.c
b/drivers/plat
The Cypress trackpad on smbus is used on other systems
as well. Lets make the name more generic.
Signed-off-by: Benson Leung
---
drivers/platform/x86/chromeos_laptop.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/platform/x86/chromeos_laptop.c
b/drivers/platfo
Two legacy Chromebooks, the Cr-48, and the Acer AC700,
are equipped with a Taos tsl2563 light sensor.
This will instantiate the sensor on those laptops.
Signed-off-by: Benson Leung
---
drivers/platform/x86/chromeos_laptop.c | 26 ++
1 file changed, 26 insertions(+)
diff
This patch series will add support for the following devices on
the following laptops:
Acer C7 Chromebook - Cypress APA Smbus Trackpad
Acer AC700 - Taos tsl2563 light sensor
Samsung Series 5 Chromebook - Taos tsl2583 light sensor
Cr-48 - Taos tsl2563 light sensor
Cheers,
Benson
--
To unsubscribe
On Fri, 2013-02-01 at 12:34 -0500, Chris Metcalf wrote:
> Using pr_info in a header exposes us to potential trouble from
> subsystems that define pr_fmt. This change fixes:
>
> In file included from include/linux/scatterlist.h:10,
>from include/scsi/scsi.h:12,
>
On Fri, Feb 1, 2013 at 12:55 PM, Joe Lawrence wrote:
> On Thu, 31 Jan 2013, Myron Stowe wrote:
>> PCI: ASPM exit link state code is skipping devices
>>
>> From: Myron Stowe
>>
>> On PCI bus hotplug removal, 'pcie_aspm_exit_link_state' can potentially
>> skip parent devices that have link_state a
>
> Also, don't forget to add the mutex protection that I suggested in another
> email.
Will do.
Thanks,
Seiji
--
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/majordo
On Friday, February 01, 2013 08:08:42 AM Viresh Kumar wrote:
> On 1 February 2013 08:01, Viresh Kumar wrote:
> > Really!! I see bleeding edge as df0e3f4 and i don't see the $(subject) patch
> > in it :)
>
> Well it might have been dropped by Rafael due to build error,
Precisely.
> which would b
On Friday, February 01, 2013 08:43:09 AM Yasuaki Ishimatsu wrote:
> Hi Rafael,
>
> 2013/02/01 5:21, Rafael J. Wysocki wrote:
> > On Thursday, January 31, 2013 12:22:14 PM Yasuaki Ishimatsu wrote:
> >> I fogot to change subject. So I resend a patch.
> >
> > I have applied patches [1-3/4] to my blee
On 02/01/2013 07:40 PM, Len Brown wrote:
> On 02/01/2013 03:44 AM, Daniel Lezcano wrote:
>> On 02/01/2013 05:11 AM, Len Brown wrote:
>>> From: Len Brown
>>>
>>> The commit, 4202735e8ab6ecfb0381631a0d0b58fefe0bd4e2
>>> (cpuidle: Split cpuidle_state structure and move per-cpu statistics fields)
>>>
On Fri, 2013-02-01 at 21:06 +, Seiji Aguchi wrote:
> > > +#include
> > > +#include
> > > +
> > > +static struct desc_ptr trace_idt_descr = { NR_VECTORS * 16 - 1,
> > > + (unsigned long) trace_idt_table };
> > > +
> > > +#ifndef CONFIG_X86_64
> > > +gate_desc trace_
On Friday, February 01, 2013 01:40:10 PM Toshi Kani wrote:
> On Fri, 2013-02-01 at 07:30 +, Greg KH wrote:
> > On Thu, Jan 31, 2013 at 06:32:18PM -0700, Toshi Kani wrote:
> > > This is already done for PCI host bridges and platform devices and I
> > don't
> > > > see why we can't do that for
On Fri, 1 Feb 2013 16:08:15 +0100
Christian Gmeiner wrote:
> ping
Bryan is handling LEDs patches (see ./MAINTAINERS). Without a cc he
presumably missed this in the lkml flood.
> 2013/1/23 GMEINER.Christian :
> >> -Urspr__ngliche Nachricht-
> >> Von: Christian Gmeiner [mailto:christian.
On 02/01/13 13:07, Anca Emanuel wrote:
> Joe, read lkml and decide after that.
> I fully apove the pathch.
>
> Reviewed-by: Anca Emanuel
>
> Review-requested-by: Joe Perches
>
>
> Comments:
> You have 3 kernels to maintain as stable, plus drivers, plus etc.
> If somebody post something withou
If stmmac_dvr_probe() fails in stmmac_pci_probe(), it breaks off initialization,
deallocates all resources, but returns zero.
The patch adds -ENODEV as return value in this case.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/net/eth
On Friday, February 01, 2013 08:23:12 AM Greg KH wrote:
> On Thu, Jan 31, 2013 at 09:54:51PM +0100, Rafael J. Wysocki wrote:
> > > > But, again, I'm going to ask why you aren't using the existing cpu /
> > > > memory / bridge / node devices that we have in the kernel. Please use
> > > > them, or g
* Philip Avinash [130123 01:28]:
> With recent GPMC driver conversion, usage of gpmc_save/restore_context
> can done from gpmc driver itself. Hence removes the usage from pm34xx.c.
> Also removes the conditional compilation primitives ARCH_OMAP3 for
> gpmc_save/restore_context.
Hmm I think this w
On Thu, 31 Jan 2013 18:44:46 -0800
Mukesh Rathor wrote:
> On Thu, 31 Jan 2013 18:30:15 -0800
> Mukesh Rathor wrote:
>
> > This patch fixes a fixme in Linux to use alloc_xenballooned_pages()
> > to allocate pfns for grant table pages instead of kmalloc. This also
> > simplifies add to physmap on
On 01/31/2013 12:52 PM, Alex Williamson wrote:
> On Thu, 2013-01-31 at 22:00 +0200, Gleb Natapov wrote:
>> On Thu, Jan 31, 2013 at 02:34:27PM -0500, Don Zickus wrote:
>>> On Thu, Jan 31, 2013 at 08:52:00PM +0200, Gleb Natapov wrote:
> http://www.invisiblethingslab.com/resources/2011/Software%20
* Philip Avinash [130117 21:00]:
> In case ELM module available, omap2 NAND driver can opt for hardware
> correction method for bit flip errors in NAND flash with BCH. Hence the
> detection of ELM module is done through devicetree population of elm_id.
> This patch update device tree documentation
1 - 100 of 650 matches
Mail list logo
