On Wed, 2014-02-19 at 21:20 -0500, Josh Boyer wrote:
> We've had a rather weird report[1] of the brightness adjustments being
> broken in a specific case with Thinkpad x220 hardware (SandyBridge
> based). If you boot the machine with it in a dock and then undock,
> the brightness adjustments do
On 02/18/2014 07:29 PM, Matthias Brugger wrote:
Commit 438e0bff5257 added the timer-keystone device driver but make use
of an unnecessary variable in the init function.
This patch delets this variable.
Signed-off-by: Matthias Brugger
Applied to my tree for 3.15.
Thanks
-- Daniel
--
On 02/19/2014 07:53 PM, Steven Rostedt wrote:
> While debugging the crash with the bad nr_running accounting, I hit
> another bug where, after running my sched deadline test, I was getting
> failures to take a CPU offline. It was giving me a -EBUSY error.
>
> Adding a bunch of trace_printk()s
On Wed, 2014-02-19 at 12:17 -0800, Stephen Boyd wrote:
> On 02/19, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > Accessing GCC on MSM8974 trough < GCC_XO_CLK> lead to NULL
>
> s/trough/through/
>
> > pointer dereference. Fix this.
> >
>
> I think you want to get the XO clock from
On 2014/2/20 8:29, Shuah Khan wrote:
> On 02/18/2014 03:46 PM, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 3.10.31 release.
>> There are 26 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with these being
npig...@kernel.dk account doesn't exist.
TO+ :
a...@linux-foundation.org, ax...@kernel.dk
On Thursday, February 20, 2014 03:56:30 PM you wrote:
> From cac24db7480b10b671d05320e0cb97a7bf5d0aea Mon Sep 17 00:00:00 2001
> From: Daeseok Youn
> Date: Thu, 20 Feb 2014 15:35:14 +0900
> Subject:
On 02/19/2014 08:18 PM, Fengguang Wu wrote:
> Greetings,
>
> I got the below dmesg and the first bad commit is
[snip]
>
> sched/balance: add balance_interval to tuning top level balance frequency
>
Good catching! :)
I will fix this problem and updated soon.
--
Thanks
Alex
--
To
Hi,
This patch set mostly cleanups memcg slab caches creation/destruction
paths fixing a couple of bugs in the meanwhile. The only serious change
it introduces is a rework of the sysfs layout for memcg slub caches (see
patch 7).
Changes in v3 (thanks to Michal Hocko):
- improve patch
When a kmem cache is created (kmem_cache_create_memcg()), we first try
to find a compatible cache that already exists and can handle requests
from the new cache, i.e. has the same object size, alignment, ctor, etc.
If there is such a cache, we do not create any new caches, instead we
simply
Currently, memcg_unregister_cache(), which deletes the cache being
destroyed from the memcg_slab_caches list, is called after
__kmem_cache_shutdown() (see kmem_cache_destroy()), which starts to
destroy the cache. As a result, one can access a partially destroyed
cache while traversing a
Currently we destroy children caches at the very beginning of
kmem_cache_destroy(). This is wrong, because the root cache will not
necessarily be destroyed in the end - if it has aliases (refcount > 0),
kmem_cache_destroy() will simply decrement its refcount and return. In
this case, at best we
Memcg-awareness turned kmem_cache_create() into a dirty interweaving of
memcg-only and except-for-memcg calls. To clean this up, let's move
the code responsible for memcg cache creation to a separate function.
Signed-off-by: Vladimir Davydov
---
include/linux/memcontrol.h |6 --
Otherwise, kzalloc() called from a memcg won't clear the whole object.
Signed-off-by: Vladimir Davydov
---
mm/slub.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/mm/slub.c b/mm/slub.c
index 2f40e615368f..cac2ff7fd68c 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -3748,7
Currently, we try to arrange sysfs entries for memcg caches in the same
manner as for global caches. Apart from turning /sys/kernel/slab into a
mess when there are a lot of kmem-active memcgs created, it actually
does not work properly - we won't create more than one link to a memcg
cache in case
This patch cleanups the memcg cache creation path as follows:
- Move memcg cache name creation to a separate function to be called
from kmem_cache_create_memcg(). This allows us to get rid of the
mutex protecting the temporary buffer used for the name formatting,
because the whole cache
On 02/19/2014 09:00 PM, Fengguang Wu wrote:
> bc575710efe937e 7511dd0a73aaf2ca4bcd829f9
> --- -
> 2029 ~ 0%+222.9% 6551 ~17%
> lkp-snb01/micro/will-it-scale/pthread_mutex2
> 143678 ~42% +4.8e+05% 6.927e+08 ~ 0%
>
From: Randy Dunlap
Date: Wed, 19 Feb 2014 07:08:09 -0800
> on i386:
>
> net/built-in.o:(.rodata+0x1707c): undefined reference to
> `ip_tunnel_get_stats64'
>
> Full randconfig file is attached.
Thanks for the report Randy, this should do it:
diff --git a/net/ipv4/ip_tunnel.c
Since commit 77873803363c "net_dma: mark broken" we no longer pin dma
engines active for the network-receive-offload use case. As a result
the ->free_chan_resources() that occurs after the driver self-test no
longer has a NET_DMA induced ->alloc_chan_resources() to back it up. A
late firing irq
On Wed, Feb 19, 2014 at 6:05 AM, Jason Gunthorpe
wrote:
> On Tue, Feb 18, 2014 at 02:32:58PM -0700, Bjorn Helgaas wrote:
>> [+cc Arnd]
>>
>> On Sun, Feb 16, 2014 at 8:33 AM, Srikanth Thokala wrote:
>> > This is the driver for Xilinx AXI PCIe Host Bridge Soft IP
>> >
>> > Signed-off-by: Srikanth
On Wed, Feb 12, 2014 at 10:07:46AM -0800, Joe Perches wrote:
> On Wed, 2014-02-12 at 18:59 +0100, Paweł Sikora wrote:
> > On Wednesday 12 of February 2014 09:46:26 Joe Perches wrote:
> > > On Wed, 2014-02-12 at 18:16 +0100, Paweł Sikora wrote:
> > > > [16855.582522] list passed to list_sort() too
(more than usual) the powerpc allyesconfig build.
Changes since 20140219:
New tree: clang
The imx-mxs tree gained a conflict against the arm-soc tree.
The powerpc tree still had its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The hid t
>From cac24db7480b10b671d05320e0cb97a7bf5d0aea Mon Sep 17 00:00:00 2001
From: Daeseok Youn
Date: Thu, 20 Feb 2014 15:35:14 +0900
Subject: [PATCH] block: replace obsolete simple_strtol() with kstrtoul()
- Makes rd_size value as static, because it is only
referenced in this file.
Signed-off-by:
Hi Randy,
On Wed, 19 Feb 2014 21:41:36 -0800 Randy Dunlap wrote:
>
> on i386:
> (from linux-next)
>
> CC sound/soc/intel/sst-dsp.o
> sound/soc/intel/sst-dsp.c: In function 'sst_dsp_outbox_write':
> sound/soc/intel/sst-dsp.c:218:2: error: implicit declaration of function
> 'memcpy_toio'
On Wed, Feb 05, 2014 at 02:19:32PM -0800, David Rientjes wrote:
> On Thu, 6 Feb 2014, Andrew Vagin wrote:
>
> > [532284.563576] BUG: unable to handle kernel paging request at
> > 35c83420
> > [532284.564086] IP: [] cpuacct_charge+0x97/0x1e0
> > [532284.564086] PGD 116369067 PUD 116368067
On Mon, Feb 17, 2014 at 10:05:49AM +0100, Krzysztof Kozlowski wrote:
> +static inline int max14577_init_eoc(struct max14577_charger *chg,
> + unsigned int uamp)
> +{
> + unsigned int current_bits = 0xf;
> + u8 reg_data;
> +
> + switch (chg->maxim_core->dev_type) {
> +
On 02/19/2014 09:10 PM, Stephane Eranian wrote:
>
> This patch updates the CBOX PMU filters mapping tables for SNB-EP
> and IVT (model 45 and 62 respectively).
>
> The NID umask always comes in addition to another umask.
> When set, the NID filter is applied.
Do you means the NID always applies
This patch introduces BQ24261 charger driver. The driver makes use of power
supply charging driver to setup charging. So the driver does hardware
abstraction and handles h/w specific corner cases. The charging logic resides
with power supply charging driver
Signed-off-by: Jenny TC
---
As per Product Safety Engineering (PSE) specification for battery charging, the
battery characteristics and thereby the charging rates can vary on different
temperature zones. This patch introduces a PSE compliant charging algorithm with
maintenance charging support. The algorithm can be selected
Add new power supply properties for input current, charge termination
current, min and max temperature
POWER_SUPPLY_PROP_TEMP_MIN - minimum operatable temperature
POWER_SUPPLY_PROP_TEMP_MAX - maximum operatable temperature
POWER_SUPPLY_PROP_INLMT - input current limit programmed by charger.
v1: introduced feature as a framework within power supply class driver with
separate files for battid framework and charging framework
v2: fixed review comments, moved macros and inline functions to power_supply.h
v3: moved the feature as a separate driver, combined battid framework and
On Tue, 18 Feb 2014 15:16:50 -0800
Andrew Morton wrote:
> On Sun, 16 Feb 2014 20:31:01 +0800 Fabian Frederick wrote:
>
> > Any user can display extented attribute names without read
> > access.
> >
> > eg: attr -l
> >
> > This patch checks inode_permission in listxattr common
> > function
On 02/19/14 16:08, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2014-02-19-16-07 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
On Tue, Feb 04, 2014 at 12:36:40PM +0100, Pavel Machek wrote:
> > --- a/drivers/power/Kconfig
> > +++ b/drivers/power/Kconfig
> > @@ -22,6 +22,19 @@ config POWER_SUPPLY_CHARGER
> > drivers to keep the charging logic outside and the charger driver
> > just need to abstract the charger
On Wed, Feb 19, 2014 at 11:15:29AM +0100, Alexander Gordeev wrote:
> As result deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() and
On Wednesday 19 February 2014 Randy Dunlap did write:
Lets start with a clean slate here. See the image from trying to boot
a 3.13.3 made from the repaired 3.12.9 .config file via an edit to
re-enable the missing media stuffs followed by a make oldconfig.
Fresh boot pix, not as well focused
On Tue, Feb 04, 2014 at 12:36:21PM +0100, Pavel Machek wrote:
> > +#define BQ24261_MIN_CV 3500
> > +#define BQ24261_MAX_CV 4440
>
> Other defines use uV as an unit :-(.
uV is used if the value is read from psy class. For register configurations
uses mV. Will change the name to reflect mV
> > +
Commit-ID: 3af7111e2066a641510c16a4e9e82dd81550115b
Gitweb: http://git.kernel.org/tip/3af7111e2066a641510c16a4e9e82dd81550115b
Author: H. Peter Anvin
AuthorDate: Wed, 19 Feb 2014 20:46:57 -0800
Committer: H. Peter Anvin
CommitDate: Wed, 19 Feb 2014 20:46:57 -0800
mm: Clean up style in
On Wed, 19 Feb 2014, Luiz Capitulino wrote:
> > Yes, my concrete objection is that the command line interface is
> > unnecessary if you can dynamically allocate and free 1GB pages at runtime
> > unless memory will be so fragmented that it cannot be done when userspace
> > is brought up. That
On Wed, 19 Feb 2014 19:46:41 -0800 (PST)
David Rientjes wrote:
> On Wed, 19 Feb 2014, Marcelo Tosatti wrote:
>
> > We agree that, in the future, we'd like to provide the ability to
> > dynamically allocate and free 1GB pages at runtime.
> >
> > Extending the kernel command line interface is a
On Wed, Feb 19, 2014 at 8:01 PM, Paul E. McKenney
wrote:
>
> The control dependency should order subsequent stores, at least assuming
> that "a" and "b" don't start off with identical stores that the compiler
> could pull out of the "if" and merge. The same might also be true for ?:
> for all I
On Thu, 2014-02-20 at 01:00 +0100, Thomas Gleixner wrote:
> On Wed, 19 Feb 2014, Mike Galbraith wrote:
> > I'm seeing ksoftirqd chewing 100% CPU on one or more CPUs in both 3.12
> > and 3.13, as below in a 40 core (+smt) box. It should look very
> > familiar to CCs, especially Ingo.
> >
> >
On 02/20/2014 02:08 AM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest, running latest
> -next kernel, I see to hit the following hang quite often.
Fix for the stuck issue around idle_balance() is now in progress, this
may caused be the same problem, I
Alexander Gordeev writes:
> As result deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() and pci_enable_msix_range()
> interfaces.
>
> Signed-off-by:
On February 19, 2014 7:54:31 PM PST, Mark Brown wrote:
>On Tue, Feb 18, 2014 at 03:22:12PM +, Charles Keepax wrote:
>> snd_soc_dapm_sync takes the dapm_mutex internally, but we currently
>take
>> it externally as well. This patch fixes this.
>
>Dimitry, are you OK with this being merged via
On Wed, Feb 19, 2014 at 09:55:21PM -0500, Peter Hurley wrote:
> On 02/19/2014 06:06 PM, Hal Murray wrote:
> >> Can you give me an idea of your device's average and minimum required
> >> latency (please be specific)? Is your target arch x86 [so I can evaluate
> >> the
> >> the impact of
On Thu, Feb 20, 2014 at 12:24 AM, Greg KH wrote:
> On Wed, Feb 19, 2014 at 12:49:33PM +0900, SeongJae Park wrote:
>> 2 debugging messages were just commented out for normal case. Let them
>> be activated on debug mode without explicit code modification.
>
> Are you sure this doesn't just always
Ping, David?
On Mon, Feb 10, 2014 at 9:37 PM, Thierry Reding
wrote:
> On Sun, Feb 09, 2014 at 06:43:18PM +0900, Alexandre Courbot wrote:
>> Declare 'struct device' explicitly in ttm_page_alloc.h as this file
>> does not include any file declaring it. This removes the following
>> warning:
>>
>>
Thanks very much. I will try out the things you mention and let you
know if I make progress.
-- Tim
On Wed, Feb 19, 2014 at 6:58 AM, Ivan T. Ivanov wrote:
>
> Hi Tim,
>
> On Tue, 2014-02-18 at 22:21 -0800, Tim Bird wrote:
>> Ivan,
>>
>> I'm having tremendous problems getting this driver to
Hi Lee,
On Mon, 17 Feb 2014 14:14:46 +1100 Stephen Rothwell
wrote:
>
> On Fri, 14 Feb 2014 13:42:17 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the mfd-lj tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > In file included from
On Wed, Feb 19, 2014 at 04:53:49PM -0800, Linus Torvalds wrote:
> On Tue, Feb 18, 2014 at 11:47 AM, Torvald Riegel wrote:
> > On Tue, 2014-02-18 at 09:44 -0800, Linus Torvalds wrote:
> >>
> >> Can you point to it? Because I can find a draft standard, and it sure
> >> as hell does *not* contain
Hi Sudeep,
Thanks for your comments, please refer to the replies below. :)
On 2014年02月19日 22:33, Sudeep Holla wrote:
Hi Hanjun,
On 18/02/14 16:23, Hanjun Guo wrote:
Get apic id from MADT or _MAT method is not implemented on arm/arm64,
and ACPI 5.0 introduces GIC Structure for it, so this
On Tue, Feb 18, 2014 at 03:22:12PM +, Charles Keepax wrote:
> snd_soc_dapm_sync takes the dapm_mutex internally, but we currently take
> it externally as well. This patch fixes this.
Dimitry, are you OK with this being merged via ASoC? The subsequent
improvements to the infrastructure and
On Wed, Feb 19, 2014 at 09:28:05AM -0800, Christoph Hellwig wrote:
> On Wed, Feb 19, 2014 at 08:22:22PM +0800, Shaohua Li wrote:
> >
> > We now have blk_mq_stop/start_queues API, delete the obsolete comments.
>
> We do have the API, but the big question is if we want to require every
> driver to
On Wed, 19 Feb 2014, Marcelo Tosatti wrote:
> We agree that, in the future, we'd like to provide the ability to
> dynamically allocate and free 1GB pages at runtime.
>
> Extending the kernel command line interface is a first step.
>
> Do you have a concrete objection to that first step ?
>
Current kprobes in-kernel page fault handler doesn't
expect that its single-stepping can be interrupted by
an NMI handler which may cause a page fault(e.g. perf
with callback tracing).
In that case, the page-fault handled by kprobes and it
misunderstands the page-fault has been caused by the
Since the NMI handlers(e.g. perf) can interrupt in the
single stepping (or preparing the single stepping, do_debug
etc.), we should consider a kprobe is hit in the NMI
handler. Even in that case, the kprobe is allowed to be
reentered as same as the kprobes hit in kprobe handlers
(KPROBE_HIT_ACTIVE
The following series fixes bugs hidden in the ancient code.
The bugs suddenly appeared when I enabled over 6,000 kprobes
and ran perf-top with --call-graph. The bugs are hidden in
the old code and it have woken up by real stress testing.
Actually, current kprobes doesn't expect an NMI handler
1: vmlinux symtab matches kallsyms: Ok
2: detect open syscall event : Ok
3: detect open syscall event on all cpus : Ok
4: read samples using the mmap interface : Ok
5: parse events tests
On Thu, Feb 20, 2014 at 11:44:32AM +0900, Mark Brown wrote:
> On Thu, Feb 20, 2014 at 02:06:20AM +, li.xi...@freescale.com wrote:
>
> > I'm not very sure of this patch, maybe should we add one menu
> > in Kconfig for all visible CPU DAIs firstly like for code drivers?
>
> Allowing them to be
Sasha reported:
[ 522.645288] BUG: unable to handle kernel NULL pointer dereference at ...
[ 522.646271] IP: [] check_preempt_wakeup+0x11f/0x210
...
[ 522.650021] Call Trace:
[ 522.650021]
[ 522.650021] [] check_preempt_curr+0x3d/0xb0
[ 522.650021] []
Hi all,
Can everyone tell me about kernel module(s) that related to permission
or privilege of user (root, normal users) in Linux.
I want to research about permission module and do some modifications
to the kernel. In fact, I want to limit root's privilege on a specific
file or folder. So, can
On Wed, 5 Feb 2014, Nishanth Menon wrote:
> omap3_noncore_dpll_set_rate forces a reparent to the same clk_ref
> for every call that takes place. This is an can be done only if a change
> is detected.
>
> Signed-off-by: Nishanth Menon
Queued for v3.15 with Tero's ack unless the patch is updated
On Wed, 2014-02-19 at 19:43:15 +0800, One Thousand Gnomes wrote:
> On Wed, 19 Feb 2014 09:14:19 +0800
> "Zhao\, Gang" wrote:
>
>> Alan, thanks for resending this patch. But it seems you overlooked
>> something we discussed earlier.
>>
>> On Mon, 2014-02-17 at 22:13:08 +0800, Alan wrote:
>> > We
used the sound-asoc tree from next-20140219 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgp5fETrl2CAS.pgp
Description: PGP signature
Hi all,
After merging the sound-asoc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
sound/soc/codecs/cs42l51.c: In function 'cs42l51_probe':
sound/soc/codecs/cs42l51.c:490:26: warning: unused variable 'cs42l51'
[-Wunused-variable]
struct cs42l51_private *cs42l51 =
On 02/19/2014 06:06 PM, Hal Murray wrote:
Can you give me an idea of your device's average and minimum required
latency (please be specific)? Is your target arch x86 [so I can evaluate the
the impact of bus-locked instructions relative to your expected]?
The code I'm familiar with is ntpd and
On Wed, Feb 19, 2014 at 06:20:13PM -0700, Shuah Khan wrote:
> Right. I think this message should be a warning instead of an error.
> Error is too alarming, unless there is a good reason for it to be an
> error.
Patches welcome...
signature.asc
Description: Digital signature
On Thu, Feb 20, 2014 at 08:50:10AM +0800, Xiubo Li wrote:
> This resend version just rewrites the commit comment.
I've applied this but I updated the commit log further - part of the
reason this didn't get applied first time around was that it says it's a
fix but it's actually a coding style
On Thu, Feb 20, 2014 at 02:06:20AM +, li.xi...@freescale.com wrote:
> I'm not very sure of this patch, maybe should we add one menu
> in Kconfig for all visible CPU DAIs firstly like for code drivers?
Allowing them to be individually selected is definitely useful if people
are trying to
On Wed, Feb 19, 2014 at 5:04 PM, Peter Zijlstra wrote:
> On Wed, Feb 19, 2014 at 01:20:30PM +0800, Lei Wen wrote:
>> Since cpu which is put into quiescent mode, would remove itself
>> from kernel's sched_domain. So we could use search sched_domain
>> method to check whether this cpu don't want to
On Wed, Feb 19, 2014 at 05:04:22PM -0700, Jon Mason wrote:
> On Tue, Feb 18, 2014 at 11:18 PM, WANG Chao wrote:
> > Hi, All
> >
> > arch/x86/kernel/pci-calgary.c is the only user of saved_max_pfn today:
> >
> > int __init detect_calgary(void)
> > {
> > [..]
> >
On 2014/2/19 20:25, Fengguang Wu wrote:
> Greetings,
>
> I got the below dmesg and the first bad commit is
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-next
>
> commit ace2bee8135a3dc725958b8d08c55ee9df813d39
> Author: Tejun Heo
> AuthorDate: Tue Feb 11 11:52:47 2014
On Tue, Feb 18, 2014 at 02:16:42PM -0800, David Rientjes wrote:
> On Tue, 18 Feb 2014, Marcelo Tosatti wrote:
>
> > > Lacking from your entire patchset is a specific example of what you want
> > > to do. So I think we're all guessing what exactly your usecase is and we
> > > aren't getting any
On 02/20/2014 02:10 AM, Sasha Levin wrote:
> On 02/17/2014 09:26 PM, Michael wang wrote:
>> On 02/17/2014 05:20 PM, Peter Zijlstra wrote:
>> [snip]
>> static void switched_to_fair(struct rq *rq, struct task_struct *p)
>> {
>>-if (!p->se.on_rq)
>>+struct sched_entity
Hi All,
We've had a rather weird report[1] of the brightness adjustments being
broken in a specific case with Thinkpad x220 hardware (SandyBridge
based). If you boot the machine with it in a dock and then undock,
the brightness adjustments do not work. That is with either the FN
keys or the
On 02/19/2014 04:42 PM, One Thousand Gnomes wrote:
It only has to happen *once*, not every time to screw stuff up.
If the reader isn't pulling _all_ the data out the instant it's woken,
trying to trim off one worker wakeup (by processing input at interrupt time)
is pointless.
No - because of
On 02/20/2014 12:16 AM, Peter Zijlstra wrote:
[snip]
>>
>>
>>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index 235cfa7..4445e56 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -7317,7 +7317,11 @@ static void switched_from_fair(struct rq *rq, struct
>>
Hi,
You can refer to this.
http://comments.gmane.org/gmane.linux.kernel.mmc/23838
Best Regards,
Jaehoon Chung
On 02/19/2014 10:47 PM, Zhang Yi wrote:
> Current code will exist when read eMMC 5.0, add support for it
>
> Signed-off-by: Zhang Yi
> ---
> mmc_cmds.c |3 +++
> 1 file changed,
On 2014年02月20日 08:37, Rafael J. Wysocki wrote:
On Wednesday, February 19, 2014 04:46:19 PM Sudeep Holla wrote:
On 19/02/14 16:49, Rafael J. Wysocki wrote:
On Wednesday, February 19, 2014 04:32:34 PM Sudeep Holla wrote:
On 18/02/14 13:55, Hanjun Guo wrote:
This patch just do some clean up to
Hi Mark,
I'm not very sure of this patch, maybe should we add one menu
in Kconfig for all visible CPU DAIs firstly like for code drivers?
Thanks,
--
Best Regards,
Xiubo
> Subject: [PATCH 2/2] ASoC: fsl: Make Freescale SAI/ESAI/SPDIF to be visible in
> Kconfig
>
> For simple card since the
Hi Jiri,
Today's linux-next merge of the hid tree got a conflict in
drivers/hid/hid-core.c between commit 117309c51dca ("HID: microsoft: Add
ID's for Surface Type/Touch Cover 2") from Linus' tree and commit
3faed1aff786 ("HID: hid-microsoft: Add support for scrollwheel and
special keypad keys")
Hi Jiri,
Today's linux-next merge of the hid tree got a conflict in
drivers/hid/hid-ids.h between commits adc232592337 ("[media] si4713: HID
blacklist Si4713 USB development board") and 3db187e7bf76 ("HID:
multitouch: add FocalTech FT support") from Linus' tree and commit
e932d8178667 ("HID:
[Re: [PATCH v2] rcu: ensure kernel/rcu/rcu.h can be sourced/used stand-alone]
On 19/02/2014 (Wed 17:53) Paul E. McKenney wrote:
> On Wed, Feb 19, 2014 at 02:33:27PM -0500, Paul Gortmaker wrote:
> > The kbuild test bot uncovered an implicit dependence on the
> > trace header being present before
On 02/20/2014 09:50 AM, Lai Jiangshan wrote:
> On 02/20/2014 08:11 AM, Tejun Heo wrote:
>> Hello, Lai.
>>
>> On Wed, Feb 19, 2014 at 11:47:58AM +0800, Lai Jiangshan wrote:
>>> If a worker is wokenup unexpectedly, it will start to work incorretly.
>>> Although it hardly happen, we should catch it
Since sometimes the 'config' parameter has no use, it should be NULL.
And make the code simplifier.
Signed-off-by: Xiubo Li
---
This resend version just rewrites the commit comment.
drivers/base/regmap/regmap.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git
On Wed, Feb 19, 2014 at 02:33:27PM -0500, Paul Gortmaker wrote:
> The kbuild test bot uncovered an implicit dependence on the
> trace header being present before rcu.h in ia64 allmodconfig
> that looks like this:
>
> In file included from kernel/ksysfs.c:22:0:
> kernel/rcu/rcu.h: In function
> On 20-Feb-2014, at 7:19 am, Linaro wrote:
>
>
>
>>> On 19-Feb-2014, at 10:56 pm, Stephen Warren wrote:
>>>
On 02/18/2014 09:15 PM, Viresh Kumar wrote:
> On 19-Feb-2014 1:48 AM, "Stephen Warren" wrote:
>
>> On 02/17/2014 02:20 AM, Viresh Kumar wrote:
>> On 15
> On 19-Feb-2014, at 10:56 pm, Stephen Warren wrote:
>
>> On 02/18/2014 09:15 PM, Viresh Kumar wrote:
>>> On 19-Feb-2014 1:48 AM, "Stephen Warren" wrote:
>>>
On 02/17/2014 02:20 AM, Viresh Kumar wrote:
> On 15 February 2014 05:33, Stephen Warren wrote:
> On 02/14/2014 03:23 PM,
On 02/20/2014 08:11 AM, Tejun Heo wrote:
> Hello, Lai.
>
> On Wed, Feb 19, 2014 at 11:47:58AM +0800, Lai Jiangshan wrote:
>> If a worker is wokenup unexpectedly, it will start to work incorretly.
>> Although it hardly happen, we should catch it and wait for being started
>> if it does happen.
>
On Wed, Feb 19, 2014 at 11:03 AM, Luck, Tony wrote:
>> (I'm c/c Tony here, as he also shared the same concern that I had on a
>> previous feedback about using I2C to talk with the DIMM).
>
> Correct - I've heard the same issues that reads on I2C can be misinterpreted
> as writes ... and oops, you
On Wed, Feb 19, 2014 at 03:42:27PM +0800, Xiubo Li wrote:
> Xiubo Li (4):
> ARM: dts: vf610: Add edma mux Tx and Rx support for SAI node.
> ARM: dts: vf610-twr: Enable SAI ALSA SoC DAI device
> ARM: dts: vf610-twr: Enable SGTL5000 codec.
> ARM: dts: vf610-twr: Add simple-card support.
From: Stephane Eranian
When dso__read_binary_type_filename() called, it doesn't check the
return value of filename__read_debuglink() so that it'll try to open
the debuglink file even if it doesn't exist.
Also fix return value of the filename__read_debuglink() as it always
return -1 regardless
The TUI of perf report and top support annotation, but stdio and GTK
don't. So it should be checked before calling hist_entry__inc_addr_
samples() since perf annotate need it regardless of UI and sort keys.
It caused perf annotate on ppc64 to produce zero output.
Reported-by: Anton Blanchard
When loading a dso it'll look for symbol tables of all possible types.
However it's just wasted of time to check incompatible types - like
trying kernel module when loading user library.
Cc: Stephane Eranian
Cc: Adrian Hunter
Cc: Cody P Schafer
Signed-off-by: Namhyung Kim
---
Stephane reported that perf report and annotate failed to process data
using lots of (> 500) shared libraries. It was because of the limit
on number of open files (ulimit -n).
Currently when perf loads dso, it'll look for normal and dynamic
symbol tables. And if it failed to find out both
From: Rafael J. Wysocki
Modify the SATA subsystem to add hotplug contexts to ACPI companions
of SATA devices and ports instead of registering special ACPI dock
operations using register_hotplug_dock_device().
That change will allow the entire code handling those special ACPI
dock operations to
On Thu, Feb 20, 2014 at 11:42:42AM +1100, Stephen Rothwell wrote:
> Hi Shawn,
>
> Today's linux-next merge of the imx-mxs tree got conflicts in
> arch/arm/mach-imx/Makefile and arch/arm/mach-imx/common.h between commit
> 28a9f3b078c5 ("ARM: imx6: build pm-imx6q.c independently of CONFIG_PM")
>
On Wed, Feb 19, 2014 at 11:26 AM, One Thousand Gnomes
wrote:
>> example, lots of graphics drivers provide i2c busses, and those busses
>> often contain eeproms, and, in theory, things should know that the
>> eeprom is associated with a particular graphics port, for example.
>> Unfortunately, the
On Thursday, February 20, 2014 02:23:30 AM Rafael J. Wysocki wrote:
> On Wednesday, February 19, 2014 12:01:20 PM Alan Stern wrote:
> > On Mon, 17 Feb 2014, Rafael J. Wysocki wrote:
> >
> > > From: Rafael J. Wysocki
> > >
> > > Currently, some subsystems (e.g. PCI and the ACPI PM domain) have
On 02/19/2014 05:36 PM, Mark Brown wrote:
On Wed, Feb 19, 2014 at 05:16:22PM -0700, Shuah Khan wrote:
On Intel systems, there are no dmesg regressions: emerg, crit,
alert, err are clean. No regressions in warn.
On AMD systems, the following new error messages - suspect is to
1 - 100 of 1390 matches
Mail list logo
