From: Konstantin Khlebnikov
Date: Sun, 05 May 2013 18:56:22 +0400
> This patch fixes race between inet_frag_lru_move() and inet_frag_lru_add()
> which was introduced in commit 3ef0eb0db4bf92c6d2510fe5c4dc51852746f206
> ("net: frag, move LRU list maintenance outside of rwlock")
>
> One cpu
On Fri, 3 May 2013, Marc Zyngier wrote:
> On 03/05/13 11:43, Stefano Stabellini wrote:
> > On Thu, 2 May 2013, Christopher Covington wrote:
> >>> So the virtual timer should appear to have been running even while time
> >>> is being stolen and therefore stolen time needs to be accounted via some
>
This patch fixes race between inet_frag_lru_move() and inet_frag_lru_add()
which was introduced in commit 3ef0eb0db4bf92c6d2510fe5c4dc51852746f206
("net: frag, move LRU list maintenance outside of rwlock")
One cpu already added new fragment queue into hash but not into LRU.
Other cpu found it in
On 2013-05-05 Sunday at 06:54 +0100 Al Viro wrote:
> A bunch of fixes for a moderately common class of bugs: file with
> single_open() done by its ->open() and seq_release as its ->release().
> That leaks; fortunately, it's not _too_ common (either people manage to
> RTFM that says "When
On Fri, May 03, 2013 at 12:37:14PM +0530, Srinidhi Kasagar wrote:
> On Thu, May 02, 2013 at 17:48:10 +0200, Lee Jones wrote:
> > drivers/staging/ste_rmi4/synaptics_i2c_rmi4.c:
> > In function ‘synaptics_rmi4_resume’:
> > drivers/staging/ste_rmi4/synaptics_i2c_rmi4.c:1090:18:
> >
Commit-ID: 642fb0f86fa38efefc0cf0e46ac20fa03e7f7f01
Gitweb: http://git.kernel.org/tip/642fb0f86fa38efefc0cf0e46ac20fa03e7f7f01
Author: Thomas Gleixner
AuthorDate: Fri, 3 May 2013 20:22:36 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 5 May 2013 16:06:35 +0200
tick: Use
Commit-ID: 3fa479b9a7762e12bdad2db39f983ba1b5f51ba2
Gitweb: http://git.kernel.org/tip/3fa479b9a7762e12bdad2db39f983ba1b5f51ba2
Author: Thomas Gleixner
AuthorDate: Fri, 3 May 2013 15:02:50 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 5 May 2013 16:06:27 +0200
tick: Cleanup NOHZ
On Fri, May 03, 2013 at 10:50:55AM +0900, Jonghwan Choi wrote:
> Add missing 'static' qualifiers
>
> Signed-off-by: Jonghwan Choi
Acked-by: Michael S. Tsirkin
> ---
> drivers/block/virtio_blk.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
On Sat, May 04, 2013 at 11:21:17AM -0400, Jake Champlin wrote:
> @@ -1802,10 +1803,11 @@ static inline void input_state_falling(struct
> logical_input *input)
>
> if (input->u.kbd.repeat_str[0]) {
> char *repeat_str = input->u.kbd.repeat_str;
Commit-ID: 9978ec69635548d00f7dabec95cf0412b3c313c4
Gitweb: http://git.kernel.org/tip/9978ec69635548d00f7dabec95cf0412b3c313c4
Author: Thomas Gleixner
AuthorDate: Fri, 3 May 2013 20:22:36 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 5 May 2013 14:44:08 +0200
tick: Use
Commit-ID: d3d233f5e55c688ea3f17a3efeb4c044f749ff55
Gitweb: http://git.kernel.org/tip/d3d233f5e55c688ea3f17a3efeb4c044f749ff55
Author: Thomas Gleixner
AuthorDate: Fri, 3 May 2013 15:02:50 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 5 May 2013 14:42:43 +0200
tick: Cleanup NOHZ
On Thu, Dec 13, 2012 at 07:14:49PM +0100, Alessandro Rubini wrote:
> This is a long-standing problem, but with not practical effects. I
> proposed a pair of different fixes quite some months ago. I'll respin
> the problem tomorrow.
Did this got fixed in some tree in the meantime? Because I still
this message came up on debian-arm and i figured that it is worthwhile
endeavouring to get across to people why device tree cannot and will
not ever be the solution it was believed to be, in the ARM world.
[just a quick note to david who asked this question on the debian-arm
mailing list: any
Linus,
Please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/kvm-3.10-1
to receive the KVM updates for the 3.10 merge window.
Highlights of the updates are:
general:
- new emulated device API
- legacy device assignment is now optional
- irqfd interface is more generic and
Signed-off-by: Alexander Shiyan
---
arch/arc/Kconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arc/Kconfig b/arch/arc/Kconfig
index 6de5ace..491ae79 100644
--- a/arch/arc/Kconfig
+++ b/arch/arc/Kconfig
@@ -16,8 +16,6 @@ config ARC
select GENERIC_FIND_FIRST_BIT
#
On Wednesday, April 17, 2013 06:58:21 PM Rajagopal Venkat wrote:
> Devfreq core runtime suspend/resume of a device is explicitly
> handled by devfreq driver using devfreq_suspend_device() and
> devfreq_resume_device() apis typically called from runtime
> suspend/resume callbacks. This patch aims
If a device sends milliseconds too, the driver will use them if it sets
the system clock at startup (through module option hctosys).
Signed-off-by: Alexander Holler
---
drivers/rtc/rtc-hid-sensor-time.c | 37 +
include/linux/hid-sensor-ids.h| 1 +
2
drivers/rtc/hctosys (CONFIG_RTC_HCTOSYS) doesn't work for
rtc-hid-sensor-time because it will be called in late_init, and thus before
rtc-hid-sensor-time gets loaded. To set the time through
rtc-hid-sensor-time at startup, the module now checks by default if the
system time is before 1970-01-02
There is no real reason to not support 16 or 32 bit values too.
Signed-off-by: Alexander Holler
---
drivers/rtc/rtc-hid-sensor-time.c | 59 +--
1 file changed, 32 insertions(+), 27 deletions(-)
diff --git a/drivers/rtc/rtc-hid-sensor-time.c
The draft for HID-sensors (HUTRR39) currently doesn't define the range
for the attribute year. Asking one of the authors revealed that full years
(e.g. 2013 instead of just 13) were meant.
So we now allow both, 8 bit and 16 bit values for the attribute year and
assuming full years when the value
Changes to the first series:
- Patch 1 and 2 are unchanged,
- Patch 3 uses getnstimeofday() instead of do_gettimeofday() which spares
a variable and it should include all changes requested through the
review by Andrew Morton. I left in the "hacky" part but included a more
verbose comment in
On Saturday, May 04, 2013 03:23:30 PM Colin Cross wrote:
> On Sat, May 4, 2013 at 1:39 PM, Tejun Heo wrote:
> > Hello, Rafael.
> >
> > On Sat, May 4, 2013 at 12:19 PM, Rafael J. Wysocki wrote:
> >>> Heh, so you are aware of the deadlock possibilities. Good selection
> >>> of spots. For all the
Hey,
Op 05-05-13 04:42, David Miller schreef:
> 1) Several routines do not use netdev_features_t to hold such bitmasks,
>fixes from Patrick McHardy and Bjørn Mork.
>
> 2) Update cpsw IRQ software state and the actual HW irq enabling in
>the correct order. From Mugunthan V N.
>
> 3) When
On Sat, May 04, 2013 at 10:02:27PM +0800, Axel Lin wrote:
> abb->current_info_idx is used as array subscript to access volt_table,
> thus the valid value range should be 0 ... desc->n_voltages - 1.
Applied, thanks.
signature.asc
Description: Digital signature
Add support for sending UFS query requests through tagged command
queuing. This design allows queuing query requests in any open slot
along with other SCSI commands. In this way there is no need to
save a slot in the requests queue and decrease its size.
A query request is posing to a SCSI
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
HEAD: 7cc23cd6c0c7d7f4bee057607e7ce01568925717 perf/x86/intel/lbr: Demand
proper privileges for PERF_SAMPLE_BRANCH_KERNEL
Misc fixes plus a
From: libo.c...@huawei.com
We have registered msm_iommu_driver first, and need unregister it when
registered msm_iommu_ctx_driver fail
Signed-off-by: Libo Chen
---
drivers/iommu/msm_iommu_dev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/iommu/msm_iommu_dev.c
From: libo.c...@huawei.com
We don`t need to kfree drvdata before kzalloc successful
Signed-off-by: Libo Chen
---
drivers/iommu/msm_iommu_dev.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/msm_iommu_dev.c b/drivers/iommu/msm_iommu_dev.c
index
From: libo.c...@huawei.com
Sorry, I am not sure who this patch should be send to.
Libo Chen (2):
msm: iommu: add missing platform_device_unregister() in err case
msm: iommu: no need kfree before kzalloc successful
drivers/iommu/msm_iommu_dev.c | 8 +---
1 file changed, 5 insertions(+),
On Sat, May 4, 2013 at 2:16 AM, Nicholas A. Bellinger
wrote:
>> BTW, there are serious issues with casting pointers to u32s to pointers to
>> u8s
>> for the last two output parameters of iscsit_do_crypto_hash_buf() (pad_bytes
>> and data_crc):
>> 1. It's not endian-safe,
>> 2. In many cases,
We print a dump stack after idr_remove warning. This is useful to find
the faulty piece of code. Let's do the same for ida_remove, as it
would be equally useful there.
Signed-off-by: Jean Delvare
Cc: Tejun Heo
Cc: Andrew Morton
Cc: Takashi Iwai
---
lib/idr.c |1 +
1 file changed, 1
* Colin Cross wrote:
> NFS calls the freezable helpers with locks held, which is unsafe
> and caused lockdep warnings when 6aa9707 "lockdep: check that no
> locks held at freeze time" was applied (reverted in dbf520a).
> Add new *_unsafe versions of the helpers that will not run the
> lockdep
* Pavel Machek wrote:
> Hi!
>
> > >> >> --- a/kernel/exit.c
> > >> >> +++ b/kernel/exit.c
> > >> >> @@ -835,7 +835,7 @@ void do_exit(long code)
> > >> >> /*
> > >> >>* Make sure we are holding no locks:
> > >> >>*/
> > >> >> - debug_check_no_locks_held(tsk);
> > >> >>
Commit-ID: fbd44a607a1a5019bc32c3615cead8c5ee8f89c9
Gitweb: http://git.kernel.org/tip/fbd44a607a1a5019bc32c3615cead8c5ee8f89c9
Author: Thomas Gleixner
AuthorDate: Fri, 3 May 2013 20:22:36 +0200
Committer: Ingo Molnar
CommitDate: Sun, 5 May 2013 11:12:19 +0200
tick: Use
* Borislav Petkov wrote:
> On Sat, May 04, 2013 at 01:22:57AM -0700, tip-bot for Peter Zijlstra wrote:
> > Commit-ID: 0f5c78b5f33ce940034743e5f9485fc81ad75b0f
> > Gitweb:
> > http://git.kernel.org/tip/0f5c78b5f33ce940034743e5f9485fc81ad75b0f
> > Author: Peter Zijlstra
> > AuthorDate:
From: Libo Chen
mtd is just member of bcm47xxsflash, so we should free bcm47xxsflash not its
member.
Signed-off-by: Libo Chen
---
drivers/mtd/devices/bcm47xxsflash.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/devices/bcm47xxsflash.c
From: Libo Chen
There is no need to free bcom_eng if kzalloc fail
Signed-off-by: Libo Chen
---
drivers/dma/bestcomm/bestcomm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/dma/bestcomm/bestcomm.c b/drivers/dma/bestcomm/bestcomm.c
index a8c2e29..300ee2d 100644
On Sat, May 4, 2013 at 4:32 PM, Andreas Schwab wrote:
> Make sure devicetable-offsets.h is cleaned in the scripts/mod directory
>
> Signed-off-by: Andreas Schwab
Tested-by: Geert Uytterhoeven
> ---
> scripts/mod/Makefile | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git
Commit-ID: 485cf5dac2966b93ef2b6211cf2fd42d66c823e6
Gitweb: http://git.kernel.org/tip/485cf5dac2966b93ef2b6211cf2fd42d66c823e6
Author: Kevin Hilman
AuthorDate: Wed, 24 Apr 2013 17:19:13 -0700
Committer: Thomas Gleixner
CommitDate: Sun, 5 May 2013 08:29:40 +0200
idle: Fix hlt/nohlt
Commit-ID: de9de4f5f11d8c89ad3e4fad49e2ebb36630a09a
Gitweb: http://git.kernel.org/tip/de9de4f5f11d8c89ad3e4fad49e2ebb36630a09a
Author: Thomas Gleixner
AuthorDate: Fri, 3 May 2013 20:22:36 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 5 May 2013 08:15:11 +0200
tick: Use
Commit-ID: ae7868e241c015aadc8632d9fe633a102a5918f6
Gitweb: http://git.kernel.org/tip/ae7868e241c015aadc8632d9fe633a102a5918f6
Author: Thomas Gleixner
AuthorDate: Fri, 3 May 2013 15:02:50 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 5 May 2013 08:15:11 +0200
tick: Cleanup NOHZ
Hi Chris,
Can you please approve this patch and the corresponding mmc-utils patch?
Thanks,
Maya
> Maya,
>
> This looks good to me.
>
> Thanks,
>Luca
>
>> -Original Message-
>> From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
>> ow...@vger.kernel.org] On Behalf Of
Hi Chris,
Can you please approve this patch and the corresponding mmc-utils patch?
Thanks,
Maya
Maya,
This looks good to me.
Thanks,
Luca
-Original Message-
From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
ow...@vger.kernel.org] On Behalf Of me...@codeaurora.org
Commit-ID: ae7868e241c015aadc8632d9fe633a102a5918f6
Gitweb: http://git.kernel.org/tip/ae7868e241c015aadc8632d9fe633a102a5918f6
Author: Thomas Gleixner t...@linutronix.de
AuthorDate: Fri, 3 May 2013 15:02:50 +0200
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Sun, 5 May 2013
Commit-ID: de9de4f5f11d8c89ad3e4fad49e2ebb36630a09a
Gitweb: http://git.kernel.org/tip/de9de4f5f11d8c89ad3e4fad49e2ebb36630a09a
Author: Thomas Gleixner t...@linutronix.de
AuthorDate: Fri, 3 May 2013 20:22:36 +0200
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Sun, 5 May 2013
Commit-ID: 485cf5dac2966b93ef2b6211cf2fd42d66c823e6
Gitweb: http://git.kernel.org/tip/485cf5dac2966b93ef2b6211cf2fd42d66c823e6
Author: Kevin Hilman khil...@linaro.org
AuthorDate: Wed, 24 Apr 2013 17:19:13 -0700
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Sun, 5 May 2013
On Sat, May 4, 2013 at 4:32 PM, Andreas Schwab sch...@linux-m68k.org wrote:
Make sure devicetable-offsets.h is cleaned in the scripts/mod directory
Signed-off-by: Andreas Schwab sch...@linux-m68k.org
Tested-by: Geert Uytterhoeven ge...@linux-m68k.org
---
scripts/mod/Makefile | 2 ++
1
From: Libo Chen libo.c...@huawei.com
There is no need to free bcom_eng if kzalloc fail
Signed-off-by: Libo Chen libo.c...@huawei.com
---
drivers/dma/bestcomm/bestcomm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/dma/bestcomm/bestcomm.c
From: Libo Chen libo.c...@huawei.com
mtd is just member of bcm47xxsflash, so we should free bcm47xxsflash not its
member.
Signed-off-by: Libo Chen libo.c...@huawei.com
---
drivers/mtd/devices/bcm47xxsflash.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
* Borislav Petkov b...@alien8.de wrote:
On Sat, May 04, 2013 at 01:22:57AM -0700, tip-bot for Peter Zijlstra wrote:
Commit-ID: 0f5c78b5f33ce940034743e5f9485fc81ad75b0f
Gitweb:
http://git.kernel.org/tip/0f5c78b5f33ce940034743e5f9485fc81ad75b0f
Author: Peter Zijlstra
Commit-ID: fbd44a607a1a5019bc32c3615cead8c5ee8f89c9
Gitweb: http://git.kernel.org/tip/fbd44a607a1a5019bc32c3615cead8c5ee8f89c9
Author: Thomas Gleixner t...@linutronix.de
AuthorDate: Fri, 3 May 2013 20:22:36 +0200
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Sun, 5 May 2013
* Pavel Machek pa...@ucw.cz wrote:
Hi!
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -835,7 +835,7 @@ void do_exit(long code)
/*
* Make sure we are holding no locks:
*/
- debug_check_no_locks_held(tsk);
+ debug_check_no_locks_held();
* Colin Cross ccr...@android.com wrote:
NFS calls the freezable helpers with locks held, which is unsafe
and caused lockdep warnings when 6aa9707 lockdep: check that no
locks held at freeze time was applied (reverted in dbf520a).
Add new *_unsafe versions of the helpers that will not run the
We print a dump stack after idr_remove warning. This is useful to find
the faulty piece of code. Let's do the same for ida_remove, as it
would be equally useful there.
Signed-off-by: Jean Delvare jdelv...@suse.de
Cc: Tejun Heo t...@kernel.org
Cc: Andrew Morton a...@linux-foundation.org
Cc:
On Sat, May 4, 2013 at 2:16 AM, Nicholas A. Bellinger
n...@linux-iscsi.org wrote:
BTW, there are serious issues with casting pointers to u32s to pointers to
u8s
for the last two output parameters of iscsit_do_crypto_hash_buf() (pad_bytes
and data_crc):
1. It's not endian-safe,
2. In
From: libo.c...@huawei.com
Sorry, I am not sure who this patch should be send to.
Libo Chen (2):
msm: iommu: add missing platform_device_unregister() in err case
msm: iommu: no need kfree before kzalloc successful
drivers/iommu/msm_iommu_dev.c | 8 +---
1 file changed, 5 insertions(+),
From: libo.c...@huawei.com
We have registered msm_iommu_driver first, and need unregister it when
registered msm_iommu_ctx_driver fail
Signed-off-by: Libo Chen libo.c...@huawei.com
---
drivers/iommu/msm_iommu_dev.c | 1 +
1 file changed, 1 insertion(+)
diff --git
From: libo.c...@huawei.com
We don`t need to kfree drvdata before kzalloc successful
Signed-off-by: Libo Chen libo.c...@huawei.com
---
drivers/iommu/msm_iommu_dev.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/msm_iommu_dev.c
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
HEAD: 7cc23cd6c0c7d7f4bee057607e7ce01568925717 perf/x86/intel/lbr: Demand
proper privileges for PERF_SAMPLE_BRANCH_KERNEL
Misc fixes plus a
Add support for sending UFS query requests through tagged command
queuing. This design allows queuing query requests in any open slot
along with other SCSI commands. In this way there is no need to
save a slot in the requests queue and decrease its size.
A query request is posing to a SCSI
On Sat, May 04, 2013 at 10:02:27PM +0800, Axel Lin wrote:
abb-current_info_idx is used as array subscript to access volt_table,
thus the valid value range should be 0 ... desc-n_voltages - 1.
Applied, thanks.
signature.asc
Description: Digital signature
Hey,
Op 05-05-13 04:42, David Miller schreef:
1) Several routines do not use netdev_features_t to hold such bitmasks,
fixes from Patrick McHardy and Bjørn Mork.
2) Update cpsw IRQ software state and the actual HW irq enabling in
the correct order. From Mugunthan V N.
3) When sending
On Saturday, May 04, 2013 03:23:30 PM Colin Cross wrote:
On Sat, May 4, 2013 at 1:39 PM, Tejun Heo t...@kernel.org wrote:
Hello, Rafael.
On Sat, May 4, 2013 at 12:19 PM, Rafael J. Wysocki r...@sisk.pl wrote:
Heh, so you are aware of the deadlock possibilities. Good selection
of spots.
Changes to the first series:
- Patch 1 and 2 are unchanged,
- Patch 3 uses getnstimeofday() instead of do_gettimeofday() which spares
a variable and it should include all changes requested through the
review by Andrew Morton. I left in the hacky part but included a more
verbose comment in
The draft for HID-sensors (HUTRR39) currently doesn't define the range
for the attribute year. Asking one of the authors revealed that full years
(e.g. 2013 instead of just 13) were meant.
So we now allow both, 8 bit and 16 bit values for the attribute year and
assuming full years when the value
There is no real reason to not support 16 or 32 bit values too.
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
drivers/rtc/rtc-hid-sensor-time.c | 59 +--
1 file changed, 32 insertions(+), 27 deletions(-)
diff --git
drivers/rtc/hctosys (CONFIG_RTC_HCTOSYS) doesn't work for
rtc-hid-sensor-time because it will be called in late_init, and thus before
rtc-hid-sensor-time gets loaded. To set the time through
rtc-hid-sensor-time at startup, the module now checks by default if the
system time is before 1970-01-02
If a device sends milliseconds too, the driver will use them if it sets
the system clock at startup (through module option hctosys).
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
drivers/rtc/rtc-hid-sensor-time.c | 37 +
On Wednesday, April 17, 2013 06:58:21 PM Rajagopal Venkat wrote:
Devfreq core runtime suspend/resume of a device is explicitly
handled by devfreq driver using devfreq_suspend_device() and
devfreq_resume_device() apis typically called from runtime
suspend/resume callbacks. This patch aims to
Signed-off-by: Alexander Shiyan shc_w...@mail.ru
---
arch/arc/Kconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arc/Kconfig b/arch/arc/Kconfig
index 6de5ace..491ae79 100644
--- a/arch/arc/Kconfig
+++ b/arch/arc/Kconfig
@@ -16,8 +16,6 @@ config ARC
select
Linus,
Please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/kvm-3.10-1
to receive the KVM updates for the 3.10 merge window.
Highlights of the updates are:
general:
- new emulated device API
- legacy device assignment is now optional
- irqfd interface is more generic and
this message came up on debian-arm and i figured that it is worthwhile
endeavouring to get across to people why device tree cannot and will
not ever be the solution it was believed to be, in the ARM world.
[just a quick note to david who asked this question on the debian-arm
mailing list: any
On Thu, Dec 13, 2012 at 07:14:49PM +0100, Alessandro Rubini wrote:
This is a long-standing problem, but with not practical effects. I
proposed a pair of different fixes quite some months ago. I'll respin
the problem tomorrow.
Did this got fixed in some tree in the meantime? Because I still see
Commit-ID: d3d233f5e55c688ea3f17a3efeb4c044f749ff55
Gitweb: http://git.kernel.org/tip/d3d233f5e55c688ea3f17a3efeb4c044f749ff55
Author: Thomas Gleixner t...@linutronix.de
AuthorDate: Fri, 3 May 2013 15:02:50 +0200
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Sun, 5 May 2013
Commit-ID: 9978ec69635548d00f7dabec95cf0412b3c313c4
Gitweb: http://git.kernel.org/tip/9978ec69635548d00f7dabec95cf0412b3c313c4
Author: Thomas Gleixner t...@linutronix.de
AuthorDate: Fri, 3 May 2013 20:22:36 +0200
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Sun, 5 May 2013
On Sat, May 04, 2013 at 11:21:17AM -0400, Jake Champlin wrote:
@@ -1802,10 +1803,11 @@ static inline void input_state_falling(struct
logical_input *input)
if (input-u.kbd.repeat_str[0]) {
char *repeat_str = input-u.kbd.repeat_str;
-
On Fri, May 03, 2013 at 10:50:55AM +0900, Jonghwan Choi wrote:
Add missing 'static' qualifiers
Signed-off-by: Jonghwan Choi jhbird.c...@samsung.com
Acked-by: Michael S. Tsirkin m...@redhat.com
---
drivers/block/virtio_blk.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Commit-ID: 3fa479b9a7762e12bdad2db39f983ba1b5f51ba2
Gitweb: http://git.kernel.org/tip/3fa479b9a7762e12bdad2db39f983ba1b5f51ba2
Author: Thomas Gleixner t...@linutronix.de
AuthorDate: Fri, 3 May 2013 15:02:50 +0200
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Sun, 5 May 2013
Commit-ID: 642fb0f86fa38efefc0cf0e46ac20fa03e7f7f01
Gitweb: http://git.kernel.org/tip/642fb0f86fa38efefc0cf0e46ac20fa03e7f7f01
Author: Thomas Gleixner t...@linutronix.de
AuthorDate: Fri, 3 May 2013 20:22:36 +0200
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Sun, 5 May 2013
On Fri, May 03, 2013 at 12:37:14PM +0530, Srinidhi Kasagar wrote:
On Thu, May 02, 2013 at 17:48:10 +0200, Lee Jones wrote:
drivers/staging/ste_rmi4/synaptics_i2c_rmi4.c:
In function ‘synaptics_rmi4_resume’:
drivers/staging/ste_rmi4/synaptics_i2c_rmi4.c:1090:18:
warning:
On 2013-05-05 Sunday at 06:54 +0100 Al Viro wrote:
A bunch of fixes for a moderately common class of bugs: file with
single_open() done by its -open() and seq_release as its -release().
That leaks; fortunately, it's not _too_ common (either people manage to
RTFM that says When using
This patch fixes race between inet_frag_lru_move() and inet_frag_lru_add()
which was introduced in commit 3ef0eb0db4bf92c6d2510fe5c4dc51852746f206
(net: frag, move LRU list maintenance outside of rwlock)
One cpu already added new fragment queue into hash but not into LRU.
Other cpu found it in
On Fri, 3 May 2013, Marc Zyngier wrote:
On 03/05/13 11:43, Stefano Stabellini wrote:
On Thu, 2 May 2013, Christopher Covington wrote:
So the virtual timer should appear to have been running even while time
is being stolen and therefore stolen time needs to be accounted via some
other
From: Konstantin Khlebnikov khlebni...@openvz.org
Date: Sun, 05 May 2013 18:56:22 +0400
This patch fixes race between inet_frag_lru_move() and inet_frag_lru_add()
which was introduced in commit 3ef0eb0db4bf92c6d2510fe5c4dc51852746f206
(net: frag, move LRU list maintenance outside of rwlock)
On Sat, May 04, 2013 at 07:39:57AM -0400, Peter Hurley wrote:
On 05/04/2013 07:15 AM, Johan Hovold wrote:
On Sat, May 04, 2013 at 01:50:42AM +0400, Stas Sergeev wrote:
04.05.2013 00:34, Greg KH пишет:
On Fri, May 03, 2013 at 10:27:18PM +0400, Stas Sergeev wrote:
03.05.2013 21:16, Greg KH
Konstantin Khlebnikov khlebni...@openvz.org wrote:
This patch fixes race between inet_frag_lru_move() and inet_frag_lru_add()
which was introduced in commit 3ef0eb0db4bf92c6d2510fe5c4dc51852746f206
(net: frag, move LRU list maintenance outside of rwlock)
One cpu already added new fragment
Use the new generic usb-serial wait_until_sent implementation to wait
for hardware buffers to drain.
This removes the need to check the hardware buffers in chars_in_buffer
and thus removes the overhead introduced by commit 2c992cd73 (USB:
ti_usb_3410_5052: query hardware-buffer status in
Use usb-serial port rather than tty as argument to get_modem_status.
Signed-off-by: Johan Hovold jhov...@gmail.com
---
drivers/usb/serial/ftdi_sio.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
index
These patches add wait_until_sent-support to usb-serial, which removes
the need to check hardware buffers in chars_in_buffer.
This fixes a problem in ftdi_sio (since 3.7) where select or TIOCMOUTQ
would take much longer than before due the hardware buffers being
queried.
Hardware buffers are
Add wait_until_sent operation which can be used to wait for hardware
buffers to drain.
Signed-off-by: Johan Hovold jhov...@gmail.com
---
drivers/usb/serial/usb-serial.c | 17 +
include/linux/usb/serial.h | 1 +
2 files changed, 18 insertions(+)
diff --git
Add generic wait_until_sent implementation which polls for empty
hardware buffers using the new port-operation tx_empty.
The generic implementation will be used for all sub-drivers that
implement tx_empty but does not define wait_until_sent.
Signed-off-by: Johan Hovold jhov...@gmail.com
---
Use the new generic usb-serial wait_until_sent implementation to wait
for hardware buffers to drain.
This removes the need to check the hardware buffers in chars_in_buffer
and thus removes the overhead introduced by commit 263e1f9f (USB:
io_ti: query hardware-buffer status in chars_in_buffer)
No need to grab disconnect mutex in chars_in_buffer now that no
sub-driver is or should be querying hardware buffers anymore. (They
should use wait_until_sent.)
Signed-off-by: Johan Hovold jhov...@gmail.com
---
drivers/usb/serial/usb-serial.c | 11 ++-
1 file changed, 2 insertions(+), 9
Use the new generic usb-serial wait_until_sent implementation to wait
for hardware buffers to drain.
This removes the need to check the hardware buffers in chars_in_buffer
and thus removes the overhead introduced by commit 6f602912 (usb:
serial: ftdi_sio: Add missing chars_in_buffer function)
On 05/05/2013 02:20 AM, tip-bot for Thomas Gleixner wrote:
Commit-ID: ae7868e241c015aadc8632d9fe633a102a5918f6
Gitweb: http://git.kernel.org/tip/ae7868e241c015aadc8632d9fe633a102a5918f6
Author: Thomas Gleixner t...@linutronix.de
AuthorDate: Fri, 3 May 2013 15:02:50 +0200
Committer:
On Thu, May 02, 2013 at 05:16:15PM +0200, Arnd Bergmann wrote:
This makes sure the conditionals for the declaration match the
definition, so we provide the alternative
#else
#define IL_LEGACY_PM_OPS NULL
#endif
in the correct cases.
drivers/built-in.o:(.data+0x57974): undefined
On Sun, May 5, 2013 at 4:03 AM, Ingo Molnar mi...@kernel.org wrote:
Please consider pulling the latest timers-nohz-for-linus git tree from:
Ok, it seems to work for me, so pulled.
However, by work for me I mean doesn't actually seem to make any
difference for me. Maybe I'm odd, but the most
Did this got fixed in some tree in the meantime? Because I still see it on
current Linus + tip/master:
arch/x86/pci/sta2x11-fixup.c:186:2: warning: initialization from incompatible
pointer type [enabled by default]
arch/x86/pci/sta2x11-fixup.c:186:2: warning: (near initialization for
On Sun, May 05, 2013 at 10:24:22PM +0200, Alessandro Rubini wrote:
Did this got fixed in some tree in the meantime? Because I still see it on
current Linus + tip/master:
arch/x86/pci/sta2x11-fixup.c:186:2: warning: initialization from
incompatible pointer type [enabled by default]
After building 3.9 for my HP/Compaq 2510p laptop, the wireless (iwl4965)
would seemingly no longer connect. Actually, it seems that it *will*
eventually, where that is somewhere between 4 and 21+ retries (from KDE
network manager). Going back to 3.8 (and earlier) and the problem goes
away.
101 - 200 of 284 matches
Mail list logo
