Hi,
Mark Rutland wrote:
> On Mon, Jan 13, 2014 at 10:17:04AM +, Lothar Waßmann wrote:
> > This patch allows the edt-ft5x06 multitouch panel driver to be
> > configured via DT.
> >
> > Signed-off-by: Lothar Waßmann
> > ---
> > .../bindings/input/touchscreen/edt-ft5x06.txt | 31
>
ACK. OK.
-Jack
On Tue, 14 Jan 2014 20:45:36 +0100
Paul Bolle wrote:
> Building resource_tracker.o triggers a GCC warning:
> drivers/net/ethernet/mellanox/mlx4/resource_tracker.c: In
> function 'mlx4_HW2SW_CQ_wrapper':
> drivers/net/ethernet/mellanox/mlx4/resource_tracker.c:3019:16:
>
ACK. OK.
-Jack
On Tue, 14 Jan 2014 20:46:52 +0100
Paul Bolle wrote:
> Building resource_tracker.o triggers a GCC warning:
> drivers/net/ethernet/mellanox/mlx4/resource_tracker.c: In
> function 'mlx4_HW2SW_SRQ_wrapper':
> drivers/net/ethernet/mellanox/mlx4/resource_tracker.c:3202:17:
>
When two threads have the same badness score, it's preferable to kill the
thread group leader so that the actual process name is printed to the
kernel log rather than the thread group name which may be shared amongst
several processes.
This was the behavior when select_bad_process() used to do
On 1/16/2014 3:42 AM, Martin K. Petersen wrote:
"nab" == Nicholas A Bellinger writes:
nab> The issue is that existing fs/bio-integrity.c code always assumes
nab> client/initiator mode, in that it will attempt to
nab> bio_integrity_generate() protection information in the submit_bio
nab> WRITE
On Thu, 16 Jan 2014, Johannes Weiner wrote:
> > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > index a815686..b482f49 100644
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -1841,13 +1841,17 @@ static void mem_cgroup_out_of_memory(struct
> > mem_cgroup *memcg, gfp_t gfp_mask,
> >
On Thu, Jan 16, 2014 at 02:45:24PM +0800, Jason Wang wrote:
> It looks like there's no need for those two fields:
>
> - Unless there's a failure for the first refill try, rq->max should be always
> equal to the vring size.
> - rq->num is only used to determine the condition that we need to do
Hi Stephen,
my bad, i am using a new set of scripts to build the mips-next tree and
somehow got that line wrong.
we will push fixed patches to our tree hopefully by tonight.
Sorry for the hassle,
John
On 15/01/2014 06:09, Stephen Rothwell wrote:
> Hi Ralf,
>
> I noticed that there is a
I have implented an I/O scheduler in Linux 2.6.But when I use fio to
test it,the kernel message often print some words,like this
"deadline_rb: forced dispatching is broken (nr_sorted=1),please report
this"
I have no idea about it,maybe my scheduler has some problems.But I
want to know why!
Thank
If the DT is used and the CPU DAI device has only one DAI, the card
name will be like :
ALSA device list:
0: 40031000.sai-sgtl5000
And this name maybe a little ugly to some customers, so here the
card name parsing from DT node is supported.
Signed-off-by: Xiubo Li
---
Resend this
On Wed, Jan 15, 2014 at 04:18:47PM -0800, David Rientjes wrote:
> On Wed, 15 Jan 2014, Johannes Weiner wrote:
>
> > With a63d83f427fb ("oom: badness heuristic rewrite"), the OOM killer
> > tries to avoid killing privileged tasks by subtracting 3% of overall
> > memory (system or cgroup) from
> -Original Message-
> From: Rob Herring [mailto:robherri...@gmail.com]
> Sent: Wednesday, January 15, 2014 9:45 PM
> To: Zhang, Rui
> Cc: linux-kernel@vger.kernel.org; linux-a...@vger.kernel.org; linux-
> i...@vger.kernel.org; linux-...@vger.kernel.org; w...@the-dreams.de; Mark
> Brown;
On Wed, Jan 15, 2014 at 06:40:41PM -0800, David Rientjes wrote:
> When two threads have the same badness score, it's preferable to kill the
> thread group leader so that the actual process name is printed to the
> kernel log rather than the thread group name which may be shared amongst
>
It looks like there's no need for those two fields:
- Unless there's a failure for the first refill try, rq->max should be always
equal to the vring size.
- rq->num is only used to determine the condition that we need to do the refill,
we could check vq->num_free instead.
- rq->num was
Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140115:
Dropped tree: sh (complex merge conflicts against very old commits)
New tree: uml
The powerpc tree still had its build failure.
The libata tree gained a conflict against the arm-soc tree
On 01/16/14 at 02:46pm, Dave Young wrote:
> On 01/15/14 at 08:04pm, H. Peter Anvin wrote:
> > On 01/15/2014 07:03 PM, Dave Young wrote:
> > >>
> > >> making something harder to grep and less standardized is hardly cleaner
> > >> and these things compile to nothing for non-modules.
> > >
> > >
Current code has implemented asynchronous threads for dpm_suspend()
and dpm_resume(), which saved much time.
As commit 5af84b82701a and 97df8c12995 said, the total time can be
reduced significantly by running suspend and resume callbacks of
device drivers in parallel with each other.
For the
On Thu, 2014-01-16 at 10:14 +0700, Linus Torvalds wrote:
> On Thu, Jan 16, 2014 at 9:45 AM, Jason Low wrote:
> >
> > Any comments on the below change which unlocks the mutex before taking
> > the lock->wait_lock to wake up a waiter? Thanks.
>
> Hmm. Doesn't that mean that a new lock owner can
On 01/15/14 at 08:04pm, H. Peter Anvin wrote:
> On 01/15/2014 07:03 PM, Dave Young wrote:
> >>
> >> making something harder to grep and less standardized is hardly cleaner
> >> and these things compile to nothing for non-modules.
> >
> > It's not nothing, just very small increasement:
> >text
On Thu, Jan 16, 2014 at 02:03:38PM +0800, Jason Wang wrote:
> On 01/16/2014 01:47 PM, Michael S. Tsirkin wrote:
> >On Thu, Jan 16, 2014 at 12:29:35PM +0800, Jason Wang wrote:
> >>On 01/15/2014 03:21 PM, Michael S. Tsirkin wrote:
> >>>On Wed, Jan 15, 2014 at 11:36:01AM +0800, Jason Wang wrote:
>
Hi all,
After merging the final tree, today's linux-next build (arm defconfig)
produced this warning:
mm/nobootmem.c: In function 'free_low_memory_core_early':
mm/nobootmem.c:119:26: warning: unused variable 'size' [-Wunused-variable]
Introduced by commit dd3ff251123c ("mm/nobootmem:
This patch adds support for parsing following regulator contraints from device
tree blob.
1. valid modes mask (valid_modes_mask)
2. input microvolt(input_uV)
3. initial mode (initial_mode)
4. initial state (initial_state)
5. state mem (state_mem)
6. state disk (state_disk)
7. state standby
Commit-ID: 7da7c1561366ba8adb7275464ab44e84e1faa7e0
Gitweb: http://git.kernel.org/tip/7da7c1561366ba8adb7275464ab44e84e1faa7e0
Author: Bin Gao
AuthorDate: Mon, 21 Oct 2013 09:16:33 -0700
Committer: H. Peter Anvin
CommitDate: Wed, 15 Jan 2014 22:28:48 -0800
x86, tsc: Add static (MSR)
Commit-ID: da6139e49c7cb0f4251265cb5243b8d220adb48d
Gitweb: http://git.kernel.org/tip/da6139e49c7cb0f4251265cb5243b8d220adb48d
Author: Prarit Bhargava
AuthorDate: Mon, 13 Jan 2014 06:51:01 -0500
Committer: H. Peter Anvin
CommitDate: Wed, 15 Jan 2014 22:24:02 -0800
x86: Add check for
On 01/15/2014 10:20 PM, HATAYAMA Daisuke wrote:
> (2014/01/16 14:53), H. Peter Anvin wrote:
>> On 01/15/2014 08:44 PM, HATAYAMA Daisuke wrote:
>>>
>>> This is not typo in my intention.
>>>
>>> generic_processor_info() has two more cases where it ignores cpus.
>>> In either cases, printed messages
(2014/01/16 14:53), H. Peter Anvin wrote:
On 01/15/2014 08:44 PM, HATAYAMA Daisuke wrote:
This is not typo in my intention.
generic_processor_info() has two more cases where it ignores cpus.
In either cases, printed messages are tagged with "ACPI" because this
function is called when parsing
commit 43dc4e01 Limit number of reported VFs to device specific value
It doesn't work and always returns -EBUSY because VFs ware already enabled.
ixgbe_enable_sriov()
pci_enable_sriov()
sriov_enable()
{
... ..
iov->ctrl |=
Because ixgbe driver limit the max number of VF functions could be enalbed
to 63, so define one macro IXGBE_MAX_VFS_DRV_LIMIT and cleanup the const 63
in code.
v3: revised for net-next tree.
V4: remove one signoff of two.
Signed-off-by: Ethan Zhao
---
On Thursday 16 January 2014 11:35 AM, Prabhakar Lad wrote:
> From: "Lad, Prabhakar"
>
> This patch fixes following sparse warning
> davinci_mdio.c:85:27: warning: symbol 'default_pdata' was not declared.
> Should it be static?
> Also makes the default_pdata as a constant.
>
> Signed-off-by: Lad,
David,
Sorry about the signoffs, I am confused about how to sign the patch,
If I sign it with off-work mail address, some of it is done within work-hours,
maybe that why I sign if with both personal mail address and work one.
If that bother you, just remove it.
Thanks,
Ethan
On Thu, Jan 16,
From: Hongbo Zhang
Freescale DMA has a feature of BandWidth Control (ab. BWC), which is currently
256 bytes and should be changed to 1024 bytes for best DMA throughput.
Changing BWC from 256 to 1024 will improve DMA performance much, in cases
whatever one channel is running or multi channels are
From: "Lad, Prabhakar"
This patch fixes following sparse warning
davinci_mdio.c:85:27: warning: symbol 'default_pdata' was not declared. Should
it be static?
Also makes the default_pdata as a constant.
Signed-off-by: Lad, Prabhakar
---
drivers/net/ethernet/ti/davinci_mdio.c |2 +-
1 file
On 01/16/2014 01:47 PM, Michael S. Tsirkin wrote:
On Thu, Jan 16, 2014 at 12:29:35PM +0800, Jason Wang wrote:
On 01/15/2014 03:21 PM, Michael S. Tsirkin wrote:
On Wed, Jan 15, 2014 at 11:36:01AM +0800, Jason Wang wrote:
On 01/14/2014 05:52 PM, Michael S. Tsirkin wrote:
On Tue, Jan 14, 2014
On Wed, Jan 15, 2014 at 12:45:57PM +0100, Heiko Carstens wrote:
> 91c2e0bcae72 "unify compat fanotify_mark(2), switch to COMPAT_SYSCALL_DEFINE"
> added a new unified compat fanotify_mark syscall to be used by all
> architectures.
> Unfortunately the unified version merges the split mask parameter
From: ethan zhao
Date: Thu, 16 Jan 2014 12:25:01 +0800
> Signed-off-by: Ethan Zhao
> Signed-off-by: Ethan Zhao
Please don't give two signoffs for yourself, it is not appropriate at
all.
I am very genuinely curious where you got the idea to do that,
particularly as I've never seen anyone else
On 01/15/2014 08:44 PM, HATAYAMA Daisuke wrote:
>
> This is not typo in my intention.
>
> generic_processor_info() has two more cases where it ignores cpus.
> In either cases, printed messages are tagged with "ACPI" because this
> function is called when parsing ACPI MADT table in
On Wed, Jan 15, 2014 at 07:58:28PM +0200, Rakesh Pandit wrote:
> Also fix befs_iget return value if iget_locked fails.
Applied, but I really wonder if we'd made a mistake with iget{5}_locked()
API - perhaps the calling conventions returning ERR_PTR(-ENOMEM) would've
been better... Most of the
From: Hongbo Zhang
Hi Vinod Koul and Dan Williams,
Please have a look at these patches.
Note that patch 2~6 had beed sent out for upstream before, but were together
with other storage patches at that time, that was not easy for being reviewed
and merged, so I send them separately this time.
On Thu, Jan 16, 2014 at 12:29:35PM +0800, Jason Wang wrote:
> On 01/15/2014 03:21 PM, Michael S. Tsirkin wrote:
> >On Wed, Jan 15, 2014 at 11:36:01AM +0800, Jason Wang wrote:
> >>On 01/14/2014 05:52 PM, Michael S. Tsirkin wrote:
> >>>On Tue, Jan 14, 2014 at 04:45:24PM +0800, Jason Wang wrote:
>
From: Hongbo Zhang
Delete attribute DMA_INTERRUPT because fsldma doesn't support this function,
exception will be thrown if talitos is used to offload xor at the same time.
Signed-off-by: Hongbo Zhang
Signed-off-by: Qiang Liu
---
drivers/dma/fsldma.c | 31 ---
1
From: Hongbo Zhang
Methods of accessing DMA contorller registers are inconsistent, some registers
are accessed by DMA_IN/OUT directly, while others are accessed by functions
get/set_* which are wrappers of DMA_IN/OUT, and even for the BCR register, it
is read by get_bcr but written by DMA_OUT.
From: Hongbo Zhang
There are several places where descriptors are freed using identical code.
This patch puts this code into a function to reduce code duplication.
Signed-off-by: Hongbo Zhang
Signed-off-by: Qiang Liu
---
drivers/dma/fsldma.c | 38 --
1
From: Hongbo Zhang
These functions will be modified in the next patch in the series. By moving the
function in a patch separate from the changes, it will make review easier.
Signed-off-by: Hongbo Zhang
Signed-off-by: Qiang Liu
---
drivers/dma/fsldma.c | 192
From: Hongbo Zhang
The usage of spin_lock_irqsave() is a stronger locking mechanism than is
required throughout the driver. The minimum locking required should be used
instead. Interrupts will be turned off and context will be saved, it is
unnecessary to use irqsave.
This patch changes all
From: Hongbo Zhang
This patch adds suspend resume functions for Freescale DMA driver.
.prepare callback is used to stop further descriptors from being added into the
pending queue, and also issue pending queues into execution if there is any.
.suspend callback makes sure all the pending jobs are
From: Hongbo Zhang
Fix the potential risk when enable config NET_DMA and ASYNC_TX. Async_tx is
lack of support in current release process of dma descriptor, all descriptors
will be released whatever is acked or no-acked by async_tx, so there is a
potential race condition when dma engine is uesd
On Wed, Jan 15, 2014 at 08:02:03PM -0800, Paul E. McKenney wrote:
> Hello!
>
> The following five patches provide some crude timer-wheel latency patches.
> I understand that a more comprehensive solution is in progress, but in the
> meantime, these patches work well in cases where a given CPU has
Freescale IFC controller has been used for mpc8xxx. It will be used
for ARM-based SoC as well. This patch moves the driver to driver/memory
and fix the header file includes.
Also remove module_platform_driver() and instead call
platform_driver_register() from subsys_initcall() to make sure
As Freescale IFC controller has been moved to driver to driver/memory.
So enable memory driver in powerpc config
Signed-off-by: Prabhakar Kushwaha
---
Changes for v2: Sending as it is
Changes for v3: Sending as it is
arch/powerpc/configs/corenet32_smp_defconfig |1 +
In a multi-platform scenario, the hard-coded major/minor numbers in
serial drivers may conflict with each other. A typical scenario is
observed with amba-pl011 and samsung-uart drivers, both of these
drivers use same set of major/minor numbers. If both of these drivers
are enabled, probe of
On Thu, 16 Jan 2014, Xiubo Li wrote:
> If the DT is used and the CPU DAI device has only one DAI, the card
> name will be like :
>
> ALSA device list:
> 0: 40031000.sai-sgtl5000
>
> And this name maybe a little ugly to some customers, so here the
> card name parsing from DT node is
If the DT is used and the CPU DAI device has only one DAI, the card
name will be like :
ALSA device list:
0: 40031000.sai-sgtl5000
And this name maybe a little ugly to some customers, so here the
card name parsing from DT node is supported.
Signed-off-by: Xiubo Li
---
I've not submitted to linux-next before, would you pull the one wire
changes to linux-next? It has been posted and reviewed by one wire
maintainer Evgeniy Polyakov, and the 15 patch series was posted again
ready to go for GregKH to pick up. This is my one wire tree not
maintainer, and once
Quoting Christian Seiler (christ...@iwakd.de):
> Eric W. Biederman writes:
> >So hmm.
> >
> >Because it can do no harm, and because it is a regression let's remove
> >the CLONE_PARENT check and send it stable.
> >
> >diff --git a/kernel/fork.c b/kernel/fork.c
> >index 086fe73..c447fbc 100644
>
(2014/01/16 6:09), tip-bot for H. Peter Anvin wrote:
Commit-ID: 5b4d1dbc24bb6fd7179ada0f47be34e27e64decb
Gitweb: http://git.kernel.org/tip/5b4d1dbc24bb6fd7179ada0f47be34e27e64decb
Author: H. Peter Anvin
AuthorDate: Wed, 15 Jan 2014 13:02:08 -0800
Committer: H. Peter Anvin
CommitDate:
The bus_mutex needs to be taken to serialize access to a specific bus.
netlink wasn't updated when bus_mutex was added and was calling
without that lock held, and not all of the masters were holding the
bus_mutex in a search. This was causing the ds2490 hardware to stop
responding when both
Switch the code documentation format style to DocBook format, enable
DocBook documentation generation, and fix some comments.
Signed-off-by: David Fries
Acked-by: Evgeniy Polyakov
---
Documentation/DocBook/Makefile |2 +-
Documentation/DocBook/w1.tmpl | 101 +
The hardware search was failing without the COMM_RST flag. Enabled
the flag and rewrote the function to handle more than one buffer of
results and to continuing where the search left off. Remove hardware
search note from the limitations now that it works. The "w1: ds2490
USB setup fixes" change
The first line printed from w1_slave gives the context of the w1
device. So does the second line, but if the CRC check failed, the
second line contains the last successful result. It is confusing when
it prints the temperature next to the line that might be a previous
conversion and has nothing
Use a #define for the usb vendor request type, clear the status
byte and use that instead of a magic offset in checking if idle.
Signed-off-by: David Fries
Acked-by: Evgeniy Polyakov
---
drivers/w1/masters/ds2490.c | 23 +++
1 file changed, 15 insertions(+), 8
Calling usb_reset_configuration after usb_set_interface resets the
interface that was just selected, so call reset first.
Using alternative 3 greatly speeds the one wire search.
alt 0 or 1, 10ms int, 23.16 seconds
alt 2 or 3, 1ms int, 2.99 to 3.05 seconds
Use usb_interrupt_msg not usb_bulk_msg
Netlink is a socket interface and is expected to be asynchronous.
Clients can now make w1 requests without blocking by making use of the
w1_master thread to process netlink commands which was previously only
used for doing an automatic bus search.
Signed-off-by: David Fries
Acked-by: Evgeniy
Unicast one wire replies back to the sender portid to avoid multiple
programs getting each other's messages, especially as the response
can't be uniquely identified with the sequence coming from the
requesting program when both programs generate the same id. Continue
to broadcast events such as
This allows replying only to the requestor portid while still
supporting broadcasting. Pass 0 to portid for the previous behavior.
Signed-off-by: David Fries
Acked-by: Evgeniy Polyakov
---
Documentation/connector/cn_test.c |2 +-
drivers/connector/cn_proc.c| 18
Introduce new commands to add, remove, and list slave devices through
the netlink interface. This can be useful to skip the search on a
static network. They could previously only be added or removed
through automatic search or sysfs, and this allows a program to only
use netlink.
Only allocate
On Wednesday 15 January 2014 09:20 PM, Kevin Hilman wrote:
> Sekhar Nori writes:
>
>> On Wednesday 15 January 2014 07:21 PM, Linus Walleij wrote:
>>> On Wed, Jan 15, 2014 at 1:54 PM, Sekhar Nori wrote:
On Wednesday 15 January 2014 02:58 PM, Linus Walleij wrote:
>>>
> Acked-by: Linus
w1_max_slave_count is only used to abort the search early
or take a fast search (when 1), so there isn't any reason to not allow
it to be updated through sysfs. Memory is not allocated based on
the current value and 10 is a rather low base number, increasing to
64, and printing a message the
Search will detect at most max_slave_count devices per run, if there
are more pick up the next search where the previous left off.
Signed-off-by: David Fries
Acked-by: Evgeniy Polyakov
---
drivers/w1/w1.c | 18 +++---
drivers/w1/w1.h |3 +++
2 files changed, 18 insertions(+),
It's valid to set the search count to 0 to stop searching, so don't
wake up the search thread to not search.
Signed-off-by: David Fries
Acked-by: Evgeniy Polyakov
---
drivers/w1/w1.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
On 01/15/2014 03:21 PM, Michael S. Tsirkin wrote:
On Wed, Jan 15, 2014 at 11:36:01AM +0800, Jason Wang wrote:
On 01/14/2014 05:52 PM, Michael S. Tsirkin wrote:
On Tue, Jan 14, 2014 at 04:45:24PM +0800, Jason Wang wrote:
On 01/14/2014 04:25 PM, Michael S. Tsirkin wrote:
On Tue, Jan 14, 2014
Before 63706172f33 "rework kthread_stop()" kthread_should_stop()
always returned false when called from a non-kthread task, after it
would oops as a non-kthread didn't have that structure and netlink was
calling search from a thread which wasn't a kthread. 9d1817cab2f030
"w1: fix oops when
This patch series aims to extend and improve the netlink interface to
the one wire system. Netlink is exposed as a socket interface which
is normally assumed to be asynchronous which only blocks waiting on
incoming packets or a fulls end buffer, but were executed on the
calling thread. A bus
Previous logic,
if (avail > 8) {
store slave;
return;
}
send data; clear;
The logic error is, if there isn't space send the buffer and clear,
but the slave wasn't added to the now empty buffer loosing that slave
id. It also should have been "if (avail >= 8)" because when it is 8,
From: Chun-Yi Lee
This issue was found in devel-pekey branch on linux-modsign.git tree.
The x509_certificate_list includes certificate twice when the
signing_key.x509 already exists.
We can reproduce this issue by making kernel twice, the build log of
second time looks like this:
...
CHK
commit 43dc4e01 Limit number of reported VFs to device specific value
It doesn't work and always returns -EBUSY because VFs ware already enabled.
ixgbe_enable_sriov()
pci_enable_sriov()
sriov_enable()
{
... ..
iov->ctrl |=
On 01/16/2014 08:46 AM, David Miller wrote:
From: Rusty Russell
Date: Thu, 16 Jan 2014 10:25:26 +1030
Rusty Russell writes:
Jason Wang writes:
It looks like there's no need for those two fields:
- Unless there's a failure for the first refill try, rq->max should be always
equal to the
Because ixgbe driver limit the max number of VF functions could be enalbed
to 63, so define one macro IXGBE_MAX_VFS_DRV_LIMIT and cleanup the const 63
in code.
v3: revised for net-next tree.
Signed-off-by: Ethan Zhao
Signed-off-by: Ethan Zhao
---
Aaron,
Revised those patches for Dave Miller's net-next OK, passed
building. resent.
Thanks,
Ethan
On Thu, Jan 16, 2014 at 11:08 AM, Ethan Zhao wrote:
> Aaron,
> Ok, Dave Miler's net-next tree.
>
> Thanks,
> Etan
>
> On Thu, Jan 16, 2014 at 10:51 AM, Brown, Aaron F
> wrote:
>> On Thu,
In the asoc_simple_card_parse_of() will parse the device node's CPU/CODEC
DAI commone fmts, and then in asoc_simple_card_sub_parse_of() will parse
the CPU/CODEC DAI's sub-node fmts, so we can combine the info->daifmt and
info->set.fmt in asoc_simple_card_sub_parse_of() not while just before
On 01/15/2014 10:38 AM, Ingo Molnar wrote:
>
> Right, the fact that most of our MSR accesses today are
> crash-on-failure, which happens to trigger crashes on a regular
> schedule, where most of the crashes are 'harmless' situation except
> that they crash the systems for good.
>
> So I think
On 01/15/2014 07:03 PM, Dave Young wrote:
>>
>> making something harder to grep and less standardized is hardly cleaner
>> and these things compile to nothing for non-modules.
>
> It's not nothing, just very small increasement:
>text data bss dec hex filename
> 7636121
於 三，2014-01-15 於 15:09 +1030，Rusty Russell 提到：
> >
> > v2:
> > Using '$(shell /bin/pwd)' instead of '$(shell pwd)' for more
> reliable
> > between different shells
>
> Hmm, that's not a great test for equality. How about:
>
> ifneq ($(realpath .), $(realpath $(srctree)))
>
> That should
Hi Daniel,
After merging the clockevents tree, the file
drivers/clocksource/clksrc-of.c.rej appears ... it was commited as part
of commit 55af97749f2b ("Merge branch 'clockevents/3.14' of
git://git.linaro.org/people/daniel.lezcano/linux into timers/core") which
I suspect was added to the
Output error messages using structured printk in single line.
In SCSI drivers, some error messages which should be output in single line are
divided in multiple lines. When user tools handle the error messages, those
divided messages will create some inconveniences.
The reason why this problem is
From: "Paul E. McKenney"
The __run_timers() function currently steps through the list one jiffy at
a time in order to update the timer wheel. However, if the timer wheel
is empty, no adjustment is needed other than updating ->timer_jiffies.
Therefore, just before we add a timer to an empty
From: "Paul E. McKenney"
Currently, the tvec_base structure's ->active_timers field tracks only
the non-deferrable timers, which means that even if ->active_timers is
zero, there might well be non-deferrable timers in the list. This commit
therefore adds an ->all_timers field to track all the
From: Oleg Nesterov
The internal_add_timer() function updates base->next_timer only if
timer->expires < base->next_timer. This is correct, but it also makes
sense to do the same if we add the first non-deferrable timer.
Signed-off-by: Oleg Nesterov
Reviewed-by: Steven Rostedt
Signed-off-by:
From: "Paul E. McKenney"
The __run_timers() function currently steps through the list one jiffy at
a time in order to update the timer wheel. However, if the timer wheel
is empty, no adjustment is needed other than updating ->timer_jiffies.
In this case, which is likely to be common for
From: "Paul E. McKenney"
The __run_timers() function currently steps through the list one jiffy at
a time in order to update the timer wheel. However, if the timer wheel
is empty, no adjustment is needed other than updating ->timer_jiffies.
Therefore, if we just emptied the timer wheel, for
Hello!
The following five patches provide some crude timer-wheel latency patches.
I understand that a more comprehensive solution is in progress, but in the
meantime, these patches work well in cases where a given CPU has either
zero or one timers pending, which is a common case for NO_HZ_FULL
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
arch/x86/kernel/process.c: In function 'mwait_idle':
/scratch/sfr/next/arch/x86/kernel/process.c:434:3: error: implicit declaration
of function '__monitor'
Hi,
> I did a mistake in the v1 of my 'ASoC: simple-card: simplify code': I
> did not initialize the pointer to the asoc_simple_card_dai_init()
> function when DT. Then, I fixed that, and the simple card does not work
> for me.
>
> First, without any 'format' in the DT, I get a fmt for each CPU
If the CPU/CODEC DAI set_sysclk() is not support, the -ENOTSUPP will returnd.
Here do the check like set_fmt().
Signed-off-by: Xiubo Li
---
sound/soc/generic/simple-card.c | 21 +
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/sound/soc/generic/simple-card.c
Add Freescale enhanced direct memory(eDMA) controller support.
This module can be found on Vybrid and LS-1 SoCs.
Signed-off-by: Alison Wang
Signed-off-by: Jingchang Lu
---
changes in v9:
define endian's operating functions instead of macro definition.
remove the filter function, using
Signed-off-by: Jingchang Lu
---
changes in v9:
remove include/dt-bindings/dma/vf610-edma.h, the request source ID
is the same as SoC's reference manual.
changes in v8:
describe dmamux info in edma node to avoid confusion.
change eDMA requst source macro definitions.
changes in v7:
fix
This series add Freescale eDMA engine support.
Jingchang Lu (2):
ARM: dts: vf610: Add eDMA node
dma: Add Freescale eDMA engine driver support
Documentation/devicetree/bindings/dma/fsl-edma.txt | 66
arch/arm/boot/dts/vf610.dtsi | 30 ++
On Thu, 16 Jan 2014 11:31:15 +0900
Namhyung Kim wrote:
> The function handler should be unregistered when the plugin unloaded
> otherwise it'll try to access invalid memory.
>
> Reviewed-by: Jiri Olsa
> Signed-off-by: Namhyung Kim
You can add my Acked-by to patches 9-12 too.
-- Steve
> ---
On Thu, 2014-01-16 at 00:23 +0100, Daniel Borkmann wrote:
> @@ -1220,7 +1219,7 @@ static unsigned int fanout_demux_hash(struct
> packet_fanout *f,
> struct sk_buff *skb,
> unsigned int num)
> {
> - return
On Thu, Jan 16, 2014 at 9:45 AM, Jason Low wrote:
>
> Any comments on the below change which unlocks the mutex before taking
> the lock->wait_lock to wake up a waiter? Thanks.
Hmm. Doesn't that mean that a new lock owner can come in *before*
you've called debug_mutex_unlock and the lockdep
On Wed, 2014-01-15 at 20:58 -0500, Steven Rostedt wrote:
> 3.2.53-rt76-rc1 stable review patch.
> If anyone has any objections, please let me know.
Not sure this is needed without the tglx don't unconditionally raise
timer softirq patch, and with that patch applied in the form it exists
in
1 - 100 of 1886 matches
Mail list logo
