On Fri, 30.05.14 01:29, Luis R. Rodriguez (mcg...@suse.com) wrote:
> I'm cc'ing a few security folks as I'd appreciate review on the ideas here,
> in particular that of a launcher idea on system to replace alternatives on the
> ExecStart= line of a systemd service unit file, alternative ideas are
On Sat, May 31, 2014 at 10:37 PM, Leon Yu wrote:
> __sk_prepare_filter() was reworked in commit bd4cf0ed3 (net: filter:
> rework/optimize internal BPF interpreter's instruction set) so that it should
> have uncharged memory once things went wrong. However that work isn't
> complete.
> Error is ha
__sk_prepare_filter() was reworked in commit bd4cf0ed3 (net: filter:
rework/optimize internal BPF interpreter's instruction set) so that it should
have uncharged memory once things went wrong. However that work isn't complete.
Error is handled only in __sk_migrate_filter() while memory can still le
From: "hyungseoung.yoo"
Preserve the master role when SCO or eSCO is active
as this improves compatability with lots of
headset and chipset combinations.
This is one of the number of patches from the Android AOSP
common.git tree, which is used on almost all Android devices.
It looks like it woul
On Sat, May 31, 2014 at 12:34:12PM -0700, H. Peter Anvin wrote:
> Typically they are using 64-bit signed seconds.
Okay, that is what I wanted to know.
Thanks,
Richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
M
On Sat, May 31, 2014 at 05:23:02PM +0200, Arnd Bergmann wrote:
> On Saturday 31 May 2014 16:51:15 Richard Cochran wrote:
> >
> > Why are some of the time stamp expiration dates marked as "never"?
>
> It's an approximation:
Also, the term "never" might mean using arbitrarily long integers
as in A
On Sun, Jun 01, 2014 at 02:14:27AM +0200, Philipp Hachtmann wrote:
> On 01.06.2014 02:00, Peter Stuge wrote:
> >Philipp Hachtmann wrote:
> >>This patch adds a sysfs attribute "cbus" which allows to set the
> >>four CBUS pins on the FT232H.
> >
> >I think this should be implemented with the gpio sub
On Sat, 2014-05-31 at 01:37 +0300, Dmitry Kasatkin wrote:
> On 28 May 2014 18:09, Mimi Zohar wrote:
> > (UEFI) secure boot provides a signature chain of trust rooted in
> > hardware. The signature chain of trust includes the Machine Owner
> > Keys(MOKs), which cannot be modified without physical
I am not a Lawyer
But I would start asking the same questions about these files that we ask about
header files.
Is there anything in the file that is not functionally required? (I believe the
answer is no, everything there is required to be what it is to make the kernel
work)
The only poss
seccomp selects BPF only instead of whole NET
Other BPF users (like tracing filters) will select BPF only too
Signed-off-by: Alexei Starovoitov
---
arch/Kconfig |3 ++-
net/Kconfig|4
net/Makefile |2 +-
net/bpf/core.c | 21 +
4 files changed, 28 in
This patch set splits BPF out of core networking into generic component
patch #1 splits filter.c into two logical pieces: generic BPF core and socket
filters. It only moves functions around. No real changes.
patch #2 adds hidden CONFIG_BPF that seccomp/tracing can select
the split was proposed i
(Please CC me on replies, not subscribed to LKML)
Hi,
Somewhat of an odd question, but none of the files in question seem to
have a copyright header on them...
For a kernel .config file, either from one of the defconfig or any other
*config option that automates the answer:
1. What license does
Hi Alexander,
>>> The reasoning to do this is the following:
>>>
>>> - If a timeout occurs, the HCI-communication is broken afterwards and the
>>> dongle isn't usable anymore.
>>> - If it works after e.g. waiting 4s everyone is still happy but if it
>>> just breaks after only waiting 2s nothing i
On Sat, May 31, 2014 at 01:41:56AM -0700, H. Peter Anvin wrote:
> On 05/30/2014 10:54 PM, Dave Chinner wrote:
> >
> > If we are changing the in-kernel timestamp to have a greater dynamic
> > range that anything we current support on disk, then we need support
> > for all filesystems for similar tr
On Sat, May 31, 2014 at 05:37:52PM +0200, Arnd Bergmann wrote:
> On Saturday 31 May 2014 11:14:50 Dave Chinner wrote:
> > On Fri, May 30, 2014 at 05:41:14PM -0700, H. Peter Anvin wrote:
> > > On 05/30/2014 05:37 PM, Dave Chinner wrote:
> > > >
> > > > IOWs, the filesystem has to be able to reject
1) uml kernel bootmem managed through bootmem_data->node_bootmem_map,
not struct page array, so it is unnecessary.
2) the struct page array allocate has been pointer by a *loacl* pointer
struct page *map in init_maps function. The array can't be access after
the init_maps exit. As a result, there
On 01.06.2014 02:00, Peter Stuge wrote:
Philipp Hachtmann wrote:
This patch adds a sysfs attribute "cbus" which allows to set the
four CBUS pins on the FT232H.
I think this should be implemented with the gpio subsystem instead.
The GPIO subsystem seems to be made for GPIO pins connected direct
On Sun, Jun 01, 2014 at 07:34:42AM +0800, Real Name wrote:
I'm very sorry. Please ignore this email, the wrong patch had been sent
out.
> 1) uml kernel bootmem managed through bootmem_data->node_bootmem_map,
> not struct page array, so it is unnecessary.
>
> 2) the struct page array allocate has
Add missing __user macro to second parameter of ethtool_ioctl().
This removes the need for the offending (void *) cast of the user space pointer
rq->ifr_data.
Signed-off-by: James A Shackleford
---
drivers/staging/vt6655/device_main.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-
Philipp Hachtmann wrote:
> This patch adds a sysfs attribute "cbus" which allows to set the
> four CBUS pins on the FT232H.
I think this should be implemented with the gpio subsystem instead.
//Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
On 01.06.2014 01:31, Philipp Hachtmann wrote:
This patch adds a sysfs attribute "cbus" which allows to set the four CBUS
pins on the FT232H.
The patch contains a *small* error that happened when splitting up my
modifications. Next series will contain the clean variant.
--
To unsubscribe from
Hello,
On Thu, May 29, 2014 at 11:05:41AM +0200, Paolo Valente wrote:
> Unfortunately, in the following frequent case the mechanism
> implemented in CFQ for detecting cooperating processes and merging
> their queues is not responsive enough to handle also the fluctuating
> I/O pattern of the secon
On Sat, 2014-05-31 at 16:27 +0200, Andreas Noever wrote:
> Hi
>
> This is version 4 of my Thunderbolt driver for Apple hardware (see [1] for
> v3).
>
> Changes since v3:
> - Fix typos and style problems caught by Bjorn.
> - Changed the #ifdef CONFIG_ACPI block to cover the whole pci quirk.
Hi
Hi folks,
I am currently developing hardware around the FTDI FT232H chip. The chip
can be programmed into asynchronous FIFO mode by EEPROM settings. Using
it with ftdi_sio in asynchronous mode works out of the box.
1. Synchronous FIFO mode
The even more wonderful synchro
This patch adds a sysfs attribute "cbus" which allows to set the four CBUS
pins on the FT232H.
CBUS support could probably extended to all supporting FTDI chips.
Signed-off-by: Philipp Hachtmann
---
drivers/usb/serial/ftdi_sio.c | 66 ++-
drivers/usb/seri
This patch adds support for the synchronous FIFO mode of the FT232H
serial converter chip.
This might also be extended to be usable with other FTDI chips.
Signed-off-by: Philipp Hachtmann
---
drivers/usb/serial/ftdi_sio.c | 65 +--
drivers/usb/serial/ftdi_
1) uml kernel bootmem managed through bootmem_data->node_bootmem_map,
not struct page array, so it is unnecessary.
2) the struct page array allocate has been pointer by a *loacl* pointer
struct page *map in init_maps function. The array can't be access after
the init_maps exit. As a result, there
This patch was made following Greg Kroah-Hartman's
newbie guide. It is not intended to make any
logical alterations to codeflow. Of note to reviews
this patch switch's a call to kzalloc to kcalloc on
line 2837
Neil Brown gave good advice on how to align
the over-long function calls. He suggested
u
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/iio/adc/ad_sigma_delta.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/gpu/drm/radeon/r600_cp.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/atm/fore200e.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
arch/x86/math-emu/poly_tan.c |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/math-emu/
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
arch/x86/kvm/x86.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/arch
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
arch/tile/kernel/unaligned.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ar
On Saturday, May 31, 2014 06:26:01 AM Niv Yehezkel wrote:
> fixed a trivial comment typo (s/mam/map) in kernel/power/swap.c.
>
> Signed-off-by: Niv Yehezkel
Applied, thanks!
> ---
> kernel/power/swap.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/power/sw
On Saturday, May 31, 2014 10:46:36 PM Zhang Rui wrote:
> On Fri, 2014-05-30 at 04:20 +0200, Rafael J. Wysocki wrote:
> > On Friday, May 23, 2014 02:02:22 AM Zhang Rui wrote:
> > > Hi, all,
> > >
> > > Currently, PNP bus is used as the default bus for for enumerating ACPI
> > > devices with _HID/_C
Hi,
I've noticed a strange issue on my lenovo W530 laptop for a few months now.
Even with just a few percent cpu use, it spins the cpu up to it's full boost
on one or more cores, and tends to keep it there for an extended period. Ever
since my laptop has been significantly warmer, and louder th
This driver add partial support of the
maxim 1027/1029/1031. Differential mode is not
supported.
It was tested on armadeus apf27 board.
Signed-off-by: Philippe Reynes
---
.../devicetree/bindings/iio/adc/max1027-adc.txt| 22 +
drivers/iio/adc/Kconfig|9 +
dr
Hi Jonathan,
On 30/05/14 18:29, Jonathan Cameron wrote:
On May 29, 2014 10:22:00 PM GMT+01:00, Philippe Reynes wrote:
This driver add partial support of the
maxim 1027/1029/1031. Differential mode is not
supported.
It was tested on armadeus apf27 board.
Signed-off-by: Philippe Reynes
On
According to RFC1035 "[...] the total length of a domain name (i.e.,
label octets and label length octets) is restricted to 255 octets or
less."
Signed-off-by: Manuel Schölling
---
net/dns_resolver/dns_query.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/dns_res
Hello.
On 06/01/2014 01:21 AM, Peter Senna Tschudin wrote:
This patch remove variables that are initialized with a constant,
are never updated, and are only used as parameter of return.
Return the constant instead of using a variable.
The patch does more than just that, it also removes co
On Sat, May 31, 2014 at 6:17 PM, Sergei Shtylyov
wrote:
> Hello.
>
>
> On 05/31/2014 05:14 PM, Peter Senna Tschudin wrote:
>
>> This patch remove variables that are initialized with a constant,
>> are never updated, and are only used as parameter of return.
>> Return the constant instead of using
On Sat, 31 May 2014, Vlastimil Babka wrote:
> On 05/31/2014 10:33 PM, Hugh Dickins wrote:
> > On Thu, 29 May 2014, Dave Jones wrote:
> >
> >> BUG: sleeping function called from invalid context at
> >> kernel/locking/rwsem.c:47
> >> in_atomic(): 0, irqs_disabled(): 0, pid: 5787, name: trinity-c27
Hello.
On 05/31/2014 05:14 PM, Peter Senna Tschudin wrote:
This patch remove variables that are initialized with a constant,
are never updated, and are only used as parameter of return.
Return the constant instead of using a variable.
The patch does more than just that, it also removes comm
On 05/31/2014 10:33 PM, Hugh Dickins wrote:
> On Thu, 29 May 2014, Dave Jones wrote:
>
>> BUG: sleeping function called from invalid context at
>> kernel/locking/rwsem.c:47
>> in_atomic(): 0, irqs_disabled(): 0, pid: 5787, name: trinity-c27
>> Preemption disabled at:[] vtime_account_system+0x1e/0
I'm announcing the release of the 3.14.5 kernel.
All users of the 3.14 kernel series must upgrade.
The updated 3.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.14.y
and can be browsed at the normal kernel.org git web browser:
On Sat, May 31, 2014 at 10:14:04AM -0300, Peter Senna Tschudin wrote:
> This patch remove variables that are initialized with a constant,
> are never updated, and are only used as parameter of return.
> Return the constant instead of using a variable.
>
> Verified by compilation only.
>
> The coc
On Sat, 31 May 2014, Steven Rostedt wrote:
> On Sat, 31 May 2014 15:57:50 -
> Thomas Gleixner wrote:
>
> > ===
> > --- tip.orig/kernel/locking/rtmutex.c
> > +++ tip/kernel/locking/rtmutex.c
> > @@ -904,16 +904,15 @@ rt_mutex_slo
On Thu, 29 May 2014, Dave Jones wrote:
> BUG: sleeping function called from invalid context at
> kernel/locking/rwsem.c:47
> in_atomic(): 0, irqs_disabled(): 0, pid: 5787, name: trinity-c27
> Preemption disabled at:[] vtime_account_system+0x1e/0x50
> CPU: 0 PID: 5787 Comm: trinity-c27 Not tainted
Include necessary header files to avoid "should be static" sparse warning
Signed-off-by: Tair Rzayev
---
drivers/staging/wlan-ng/cfg80211.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/wlan-ng/cfg80211.c
b/drivers/staging/wlan-ng/cfg80211.c
index f76f95c..01be471 100644
Make jpeg_dqt[][] static
Signed-off-by: Tair Rzayev
---
drivers/staging/media/solo6x10/solo6x10-jpeg.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/solo6x10/solo6x10-jpeg.h
b/drivers/staging/media/solo6x10/solo6x10-jpeg.h
index c5218ce..9e41185 10064
On Sat, May 31, 2014 at 10:14:06AM -0300, Peter Senna Tschudin wrote:
> diff --git a/drivers/net/wireless/brcm80211/brcmsmac/phy/phy_cmn.c
> b/drivers/net/wireless/brcm80211/brcmsmac/phy/phy_cmn.c
> index b0fd807..57ecc05 100644
> --- a/drivers/net/wireless/brcm80211/brcmsmac/phy/phy_cmn.c
> +++ b
On Sat, May 31, 2014 at 01:18:34PM -0700, Greg KH wrote:
> On Sat, May 31, 2014 at 11:03:44PM +0300, Tair Rzayev wrote:
> >
> >
> > On 2014.05.31. 22:52, Greg KH wrote:
> > > What kernel tree did you make this against? It doesn't seem to match up
> > > with what is in my staging-next branch to m
On Sat, May 31, 2014 at 11:03:44PM +0300, Tair Rzayev wrote:
>
>
> On 2014.05.31. 22:52, Greg KH wrote:
> > What kernel tree did you make this against? It doesn't seem to match up
> > with what is in my staging-next branch to merge with Linus for the next
> > release, so please work against that
Vasily Kulikov writes:
> On Thu, May 29, 2014 at 16:53 +0400, Pavel Emelyanov wrote:
>> On 05/29/2014 03:59 PM, Vasily Kulikov wrote:
>> > On Thu, May 29, 2014 at 15:31 +0400, Pavel Emelyanov wrote:
>> >> On 05/29/2014 03:12 PM, Vasily Kulikov wrote:
>> >>> On Thu, May 29, 2014 at 13:07 +0400, Pa
On 2014.05.31. 22:52, Greg KH wrote:
> What kernel tree did you make this against? It doesn't seem to match up
> with what is in my staging-next branch to merge with Linus for the next
> release, so please work against that one.
Made against staging-next branch of your linux-next staging tree.
On Sat, 31 May 2014 15:57:51 -
Thomas Gleixner wrote:
> Add a separate local variable for the boost/deboost logic to make the
> code more readable. Add comments where appropriate.
>
> Signed-off-by: Thomas Gleixner
> Cc: Peter Zijlstra
> Cc: Steven Rostedt
Reviewed-by: Steven Rostedt
-
On Sat, 31 May 2014 15:57:49 -
Thomas Gleixner wrote:
> Index: tip/kernel/locking/rtmutex.c
> ===
> --- tip.orig/kernel/locking/rtmutex.c
> +++ tip/kernel/locking/rtmutex.c
> @@ -256,6 +256,25 @@ static void rt_mutex_adjust_prio
On Sat, 31 May 2014 15:57:48 -
Thomas Gleixner wrote:
> The tester has been broken for quite some time. It's possible to fix
> it, but the main reason for having it in the kernel was the lock steal
> mechanism in the rtmutex code. That's gone, so we can implement a
> stateful correctness test
On Sat, 31 May 2014 15:57:50 -
Thomas Gleixner wrote:
> ===
> --- tip.orig/kernel/locking/rtmutex.c
> +++ tip/kernel/locking/rtmutex.c
> @@ -904,16 +904,15 @@ rt_mutex_slowunlock(struct rt_mutex *loc
> */
> static inline int
>
On Sat, May 31, 2014 at 10:43:34PM +0300, Tair Rzayev wrote:
> Instead of getting the reference to whole credential structure, use
> task_euid() and current_euid() to get it.
>
> Signed-off-by: Tair Rzayev
> ---
> drivers/staging/android/binder.c | 14 +++---
> 1 file changed, 7 insertio
I'm announcing the release of the 3.10.41 kernel.
All users of the 3.10 kernel series must upgrade.
The updated 3.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.10.y
and can be browsed at the normal kernel.org git web browser:
Fix the over 80 character line
Signed-off-by: Tair Rzayev
---
drivers/staging/android/ion/ion_chunk_heap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/android/ion/ion_chunk_heap.c
b/drivers/staging/android/ion/ion_chunk_heap.c
index 3f2c12b..9c3e49a 10064
Instead of getting the reference to whole credential structure, use
task_euid() and current_euid() to get it.
Signed-off-by: Tair Rzayev
---
drivers/staging/android/binder.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/android/binder.c b/driv
On Sat, May 31, 2014 at 11:12 AM, mnipxh wrote:
> When pgoff_t index is 32bit, sector_t block is 64bit, need check if block
> number is too big.
> If block is bigger than (4Gb * PAGE_SIZE), index becomes a wrong value.
> Commit e5657933863f43cc6bb76a54d659303dafaa9e58 wants to do this. But it
>
Typically they are using 64-bit signed seconds.
On May 31, 2014 11:22:37 AM PDT, Richard Cochran
wrote:
>On Sat, May 31, 2014 at 05:23:02PM +0200, Arnd Bergmann wrote:
>>
>> It's an approximation:
>
>(Approximately never ;)
>
>> with 64-bit timestamps, you can represent close to 300 billion
>>
On Saturday 31 May 2014 01:36:40 Liviu Dudau wrote:
> We would like to be able to describe PCIe ECAM resources as
> IORESOURCE_MEM blocks while distinguish them from standard
> memory resources. Add an IORESOURCE_BIT entry for this case.
>
> Signed-off-by: Liviu Dudau
I still don't see any value
On Sat, May 31, 2014 at 05:23:02PM +0200, Arnd Bergmann wrote:
>
> It's an approximation:
(Approximately never ;)
> with 64-bit timestamps, you can represent close to 300 billion
> years, which is way past the time that our planet can sustain
> life of any form[1].
Did you mean mean 64 bits wor
When pgoff_t index is 32bit, sector_t block is 64bit, need check if block
number is too big.
If block is bigger than (4Gb * PAGE_SIZE), index becomes a wrong value.
Commit e5657933863f43cc6bb76a54d659303dafaa9e58 wants to do this. But it gives
an uncorrect check.
I think block != index << sizebit
Hi all,
until now, every sysadmin/distro had to update the sysv limits.
For shm, the new proposal is to increase the limits to (nearly) ULONG_MAX.
Right now, I try to create patches that also increase the limits for
sysv msg, but I got stuck:
- MSGMNI is trivial, just increase it to nearly IP
On Sat, May 31, 2014 at 04:27:45PM +0200, Andreas Noever wrote:
> Hi
>
> This is version 4 of my Thunderbolt driver for Apple hardware (see [1] for
> v3).
>
> Changes since v3:
> - Fix typos and style problems caught by Bjorn.
> - Changed the #ifdef CONFIG_ACPI block to cover the whole pci qui
Thank you Neil
I was not sure if space-based alignment was allowed so thank you for
demonstrating the change. It does make the code much easier to read.
Similar thank you for how to indent over-long function calls. I had
mis-understood the coding standard to mean overflow needed to be on
the far
Hello,
I'm writing a driver for Sony SxS cards, which is an Expresscard based
flash memory card used in Sony cameras with an eventual goal of
submitting the code to mainline.
The code in its current working but ugly state can be found here:
https://github.com/kierank/sxs-linux/blob/master/sxs.c
According to RFC1035 "[...] the total length of a domain name (i.e.,
label octets and label length octets) is restricted to 255 octets or
less."
Signed-off-by: Manuel Schölling
---
net/dns_resolver/dns_query.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/dns_resolve
blk_mq_put_ctx() has to be called before io_schedule() in
bt_get().
This patch fixes the problem by taking similar approach from
percpu_ida allocation for the situation.
Signed-off-by: Ming Lei
---
block/blk-mq-tag.c | 48 +++-
block/blk-mq-tag.h |
Hi Jens,
These two patches fix the problem of schedule from atomic context
which is introduced in bitmap based allocation.
Thanks,
--
Ming Lei
--
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
The blk-mq tag code need these helpers.
Signed-off-by: Ming Lei
---
block/blk-mq.c | 22 --
block/blk-mq.h | 22 ++
2 files changed, 22 insertions(+), 22 deletions(-)
diff --git a/block/blk-mq.c b/block/blk-mq.c
index 0f5879c..b9230c5 100644
--- a/blo
This patch remove variables that are initialized with a constant,
are never updated, and are only used as parameter of return.
Return the constant instead of using a variable.
Verified by compilation only.
The coccinelle script that find and fixes this issue is:
//
@@
type T;
constant C;
identif
This patch remove variables that are initialized with a constant,
are never updated, and are only used as parameter of return.
Return the constant instead of using a variable.
Verified by compilation only.
The coccinelle script that find and fixes this issue is:
//
@@
type T;
constant C;
identif
On Sat, May 31, 2014 at 4:54 PM, Arnd Bergmann wrote:
> On Saturday 31 May 2014 10:39:02 Andreas Schwab wrote:
>> Geert Uytterhoeven writes:
>>
>> > Hi Arnd,
>> >
>> > On Fri, May 30, 2014 at 10:01 PM, Arnd Bergmann wrote:
>> >> + * The variant using bit fields is less efficient to access, but
>
On Sat, May 31, 2014 at 12:17 PM, walter harms wrote:
>
>
> Am 31.05.2014 15:14, schrieb Peter Senna Tschudin:
>> This patch remove variables that are initialized with a constant,
>> are never updated, and are only used as parameter of return.
>> Return the constant instead of using a variable.
>>
Hello,
After returning from holiday I found this in dmesg:
[1724773.295579] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[1725207.771256] BUG: scheduling while atomic: irq/20-serial/1299/0x0202
[1725207.771260] Modules linked in: btrfs lzo_compress zlib_deflate bnep
bluetooth 6lowp
On Sat, May 31, 2014 at 10:48 AM, Linus Torvalds
wrote:
>
>
> On Sat, 31 May 2014, Josh Boyer wrote:
>>
>> One of my machines got the lockdep report below when booting a kernel
>> that contained these patches.
>
> I think this is just a lacking annotation.
>
> We do nest dentry d_lock locking, and
This patch remove variables that are initialized with a constant,
are never updated, and are only used as parameter of return.
Return the constant instead of using a variable.
Verified by compilation only.
The coccinelle script that find and fixes this issue is:
//
@@
type T;
constant C;
identif
On Sat, May 31, 2014 at 11:58 AM, Johan Hovold wrote:
> On Sat, May 31, 2014 at 10:14:01AM -0300, Peter Senna Tschudin wrote:
>> This patch remove variables that are initialized with a constant,
>> are never updated, and are only used as parameter of return.
>> Return the constant instead of using
This patch remove the function klsi_105_tiocmset which was only
returning -EINVAL. It also removes the function prototype and
the .tiocmset entry in the struct usb_serial_driver.
Verified by compilation only.
Signed-off-by: Peter Senna Tschudin
---
Changes from V1:
- remove the function klsi_1
In case the dead lock detector is enabled we follow the lock chain to
the end in rt_mutex_adjust_prio_chain, even if we could stop earlier
due to the priority/waiter constellation.
But once we are not longer the top priority waiter in a certain step
or the task holding the lock has already the sam
Changes vs. v1 [1]:
Dropped 1/N as it's queued already.
Removed the config symbols as pointed out by Steven.
Addressed the review feedback from Steven and Jason.
Thanks,
tglx
---
[1] http://lkml.kernel.org/r/20140522031841.797415...@linutronix.de
--
To unsubscribe from this list: send
Add a separate local variable for the boost/deboost logic to make the
code more readable. Add comments where appropriate.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Steven Rostedt
Cc: Lai Jiangshan
Link: http://lkml.kernel.org/r/20140522031950.168005...@linutronix.de
Signed-off-by:
The tester has been broken for quite some time. It's possible to fix
it, but the main reason for having it in the kernel was the lock steal
mechanism in the rtmutex code. That's gone, so we can implement a
stateful correctness tester just via the futex syscall.
Signed-off-by: Thomas Gleixner
Cc:
The builtin tester is gone,, so the deadlock logic is now only
required for futexes.
Remove the extra arguments for the public functions and also for the
futex specific ones which get always called with deadlock detection
enabled.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Steven Ros
The conditions under which deadlock detection is conducted are unclear
and undocumented.
Add constants instead of using 0/1 and provide a selection function
which hides the additional debug dependency from the calling code.
Add comments where needed.
Signed-off-by: Thomas Gleixner
Cc: Peter Zij
Hi,
2014-05-31 8:09 GMT+09:00 Stephen Rothwell :
> Hi,
>
> On Sat, 31 May 2014 01:12:08 +0900 jaeg...@kernel.org wrote:
>>
>> From: Jaegeuk Kim
>>
>> This patch changes the valid email address to maintain the f2fs file system.
>
> Have you remembered to notify the linux-next maintainer? :-)
Oop
Internet Account users,
This email is from our Internet web-mail Customer service and we are sending it
to every User Accounts Owner for safety,We are having congestion due to the
fraudulent e-mails to accounts owners so we are shutting down some accounts and
your account was among those to b
On Sat, 31 May 2014, H. Peter Anvin wrote:
> On 05/30/2014 10:54 PM, Dave Chinner wrote:
> >
> > If we are changing the in-kernel timestamp to have a greater dynamic
> > range that anything we current support on disk, then we need support
> > for all filesystems for similar translation and constr
This patch adds the necessary node to probe the global clock
controller on APQ8084 platforms.
Signed-off-by: Georgi Djakov
---
arch/arm/boot/dts/qcom-apq8084.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-apq8084.dtsi
b/arch/arm/boot/dts/qcom-apq80
Add the compatible string for the APQ8084 global clock controller
to the clock binding documentation.
Signed-off-by: Georgi Djakov
---
.../devicetree/bindings/clock/qcom,gcc.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/clock/qcom,gcc.txt
b
This driver adds support for USB controlled led panels that exist in MSI GT683R
laptop.
Signed-off-by: Janne Kanniainen
---
drivers/leds/Kconfig | 6 ++
drivers/leds/Makefile | 1 +
drivers/leds/leds-gt683r.c | 241 +
3 files changed, 2
Add the necessary DT node to probe the serial driver on
APQ8084 platforms.
Signed-off-by: Georgi Djakov
---
arch/arm/boot/dts/qcom-apq8084-mtp.dts |6 ++
arch/arm/boot/dts/qcom-apq8084.dtsi|8
2 files changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-apq8084
This patchset adds support for the global clock controller found on the
APQ8084 based platforms.
Patches 1,2 can go through clk-next and 3,4 through arm-soc.
Changes from v1:
- Moved APQ8084 clocks into a separate file and under separate Kconfig
entry. Dropped the override function patch from
1 - 100 of 185 matches
Mail list logo
