Linus,
please pull bugfixes for i2c-embedded. 2 patches are usual stuff. The
bigger patch is needed to correct a wrong decision made in this merge
window. We hoped to get the PIOQUEUE mode in the mxs driver working with
DMA, but it turned out to be too broken (leading to data loss), so we
now thin
On Sat, 20 Oct 2012 23:15:17 + (GMT), Artem S. Tashkinov wrote:
> It's almost definitely either a USB driver bug or video4linux driver bug:
>
> I'm CC'ing linux-media and linux-usb mailing lists, the problem is described
> here:
> https://lkml.org/lkml/2012/10/20/35
> https://lkml.org/lkml/201
On Sat, 3 Nov 2012, walter harms wrote:
Am 03.11.2012 11:58, schrieb Julia Lawall:
From: Julia Lawall
Use WARN rather than printk followed by WARN_ON(1), for conciseness.
A simplified version of the semantic patch that makes this transformation
is as follows: (http://coccinelle.lip6.fr/)
> -Original Message-
> From: Andrew Morton [mailto:a...@linux-foundation.org]
> Sent: Tuesday, October 09, 2012 3:48 PM
> To: Greg KH
> Cc: KY Srinivasan; o...@aepfle.de; linux-kernel@vger.kernel.org;
> a...@firstfloor.org; a...@canonical.com; de...@linuxdriverproject.org
> Subject: Re: [
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Friday, November 02, 2012 7:37 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org
> Subject: Re: drivres/hv
>
> On Fri, Nov 02, 2012 at 03:11:23PM -0700, K. Y. Srinivasan
On 03.11.2012 15:10, Christof Meerwald wrote:
> On Sat, 20 Oct 2012 23:15:17 + (GMT), Artem S. Tashkinov wrote:
>> It's almost definitely either a USB driver bug or video4linux driver bug:
>>
>> I'm CC'ing linux-media and linux-usb mailing lists, the problem is described
>> here:
>> https://lk
From: Julia Lawall
eprintk is really just WARN(1, KERN_ERR ...). Use WARN to be more
consistent with the rest of the code.
Signed-off-by: Julia Lawall
---
drivers/misc/kgdbts.c | 38 +-
1 file changed, 17 insertions(+), 21 deletions(-)
diff --git a/dri
On Sat, 3 Nov 2012, Daniel Mack wrote:
> On 03.11.2012 15:10, Christof Meerwald wrote:
> > On Sat, 20 Oct 2012 23:15:17 + (GMT), Artem S. Tashkinov wrote:
> >> It's almost definitely either a USB driver bug or video4linux driver bug:
> >>
> >> I'm CC'ing linux-media and linux-usb mailing lists
On Sat, Nov 03, 2012 at 09:45:02AM -0200, Rafael Aquini wrote:
> On Fri, Nov 02, 2012 at 09:07:11PM -0700, Greg Kroah-Hartman wrote:
> > >
> > > Howdy Greg,
> > >
> > > Somehow the following patch is missing for this series submission:
> > > > Len Brown
> > > > x86: Remove the ancient and de
> > It's not really about the lines of code. It adds a new userland
> > visible interface. As for the "long" list of commands, it depends on
> > how you write it but even if it's textually long it's still very
> > simple in terms of actual complexity.
>
> Sure, but its place is not the kernel.
>
On Sat, 2012-11-03 at 07:43 -0700, Greg Kroah-Hartman wrote:
> On Sat, Nov 03, 2012 at 09:45:02AM -0200, Rafael Aquini wrote:
> > On Fri, Nov 02, 2012 at 09:07:11PM -0700, Greg Kroah-Hartman wrote:
> > > >
> > > > Howdy Greg,
> > > >
> > > > Somehow the following patch is missing for this series
On Sat, Nov 3, 2012 at 12:48 PM, Mike Galbraith wrote:
> On Sat, 2012-11-03 at 04:33 -0700, Mike Galbraith wrote:
>> On Fri, 2012-11-02 at 21:09 +0100, Michal Zatloukal wrote:
>>
>> > On the new kernel, the nice processes are never starved - even when
>> > starting a tab-laden chromium session, th
This renames prandom32() and prandom32_seed to randome32_state() and
srandom32_state(). The purpose of this renaming is to prevent some
kernel developers from assuming that prandom32() and random32() might
imply that only prandom32() was the one using a pseudo-random number
generator by prandom32'
This removes home-brewed pseudo-random number generator and use
random32_get_bytes_state().
Signed-off-by: Akinobu Mita
Cc: Artem Bityutskiy
Cc: David Woodhouse
Cc: linux-...@lists.infradead.org
---
* v2
- rename prandom32_get_bytes to random32_get_bytes_state
drivers/mtd/tests/mtd_pagetest.c
This removes home-brewed pseudo-random number generator and use
random32_get_bytes_state().
Signed-off-by: Akinobu Mita
Cc: Artem Bityutskiy
Cc: David Woodhouse
Cc: linux-...@lists.infradead.org
---
* v2
- rename prandom32_get_bytes to random32_get_bytes_state
drivers/mtd/tests/mtd_subpagetes
Using random32_get_bytes() is enough. Because this data is only used
for testing, not used for cryptographic use.
Signed-off-by: Akinobu Mita
Cc: Artem Bityutskiy
Cc: David Woodhouse
Cc: linux-...@lists.infradead.org
---
no change from v1
drivers/mtd/tests/mtd_nandecctest.c | 2 +-
1 file ch
Signed-off-by: Akinobu Mita
Cc: Artem Bityutskiy
Cc: David Woodhouse
Cc: linux-...@lists.infradead.org
---
new patch from v2
drivers/mtd/tests/mtd_stresstest.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/mtd/tests/mtd_stresstest.c
b/drivers/mtd/tests/mtd_stre
Use random32_get_bytes instead of equivalent local function.
Signed-off-by: Akinobu Mita
Cc: Artem Bityutskiy
Cc: David Woodhouse
Cc: linux-...@lists.infradead.org
---
no change from v1
drivers/mtd/tests/mtd_speedtest.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git
Add functions to get the requested number of pseudo-random bytes.
The difference from get_random_bytes() is that it generates pseudo-random
numbers by random32(). It is fast, suitable for generating random bytes
for testing, and reproducible if random32_get_bytes_state() is used.
Signed-off-by:
This also removes unnecessary memset call which is immediately overwritten
with random bytes.
Signed-off-by: Akinobu Mita
Cc: Artem Bityutskiy
Cc: David Woodhouse
Cc: linux-...@lists.infradead.org
---
no change from v1
drivers/mtd/nand/nandsim.c | 5 +
1 file changed, 1 insertion(+), 4 de
This removes home-brewed pseudo-random number generator and use
random32_get_bytes_state().
Signed-off-by: Akinobu Mita
Cc: Artem Bityutskiy
Cc: David Woodhouse
Cc: linux-...@lists.infradead.org
---
* v2
- rename prandom32_get_bytes to random32_get_bytes_state
drivers/mtd/tests/mtd_oobtest.c
This also converts filling memory loop to use memset.
Signed-off-by: Akinobu Mita
Cc: Artem Bityutskiy
Cc: Adrian Hunter
Cc: linux-...@lists.infradead.org
---
no change from v1
fs/ubifs/debug.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/fs/ubifs/debug.c b/fs/u
Use random32_get_bytes() to fill rss key with pseudo-random bytes.
Signed-off-by: Akinobu Mita
Cc: Eilon Greenstein
Cc: net...@vger.kernel.org
---
new patch from v2
drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/n
This patchset introduces new functions into random32 library for
getting the requested number of pseudo-random bytes.
Before introducing these new functions into random32 library,
prandom32() and prandom32_seed() with "prandom32" prefix are
renamed to random32_state() and srandom32_state() respect
On Sat, Nov 3, 2012 at 4:51 AM, Vasiliy Kulikov wrote:
> On Thu, Nov 01, 2012 at 11:35 -0700, Kees Cook wrote:
>> @@ -327,6 +327,13 @@ static inline void task_cap(struct seq_file *m, struct
>> task_struct *p)
>> render_cap_t(m, "CapBnd:\t", &cap_bset);
>> }
>>
>> +static inline void task_s
Modern high-end servers may support advanced RAS features, such as
system device dynamic reconfiguration. On x86 and IA64 platforms,
system device means processor(CPU), memory device, PCI host bridge
and even computer node.
The ACPI specifications have provided standard interfaces between
firmware
Modern high-end servers may support advanced RAS features, such as
system device dynamic reconfiguration. On x86 and IA64 platforms,
system device means processor(CPU), memory device, PCI host bridge
and even computer node.
The ACPI specifications have provided standard interfaces between
firmware
An ACPI hotplug slot is an abstraction of receptacles, where a group of
system devices could be connected to. This patch implements the skeleton
of the ACPI system device hotplug slot enumerator. On loading, it scans
the whole ACPI namespace for hotplug slots and creates a device node for
each hotp
This patch implements a default mechanism to detect and manage ACPI
system device hotplug slots based on standard ACPI interfaces.
1) Detech hotplug slot by checking existence of _EJ0 and _STA methods.
2) Power off a slot by evaluating _EJ0 method.
It's the default hotplug slot enumerating mechani
This patch implements a fake ACPI system device hotplug slot enumerator,
which could be used to test and verify hotplug logic on platforms with
hardware hotplug capabilities.
The fake slot enumerator will be enabled by passing module parameter
"fake_slot=value". The encoding of "value" is:
0x1: fa
Create a new subsystem that probes on kernel boundaries
to keep track of the transitions between level contexts
with two basic initial contexts: user or kernel.
This is an abstraction of some RCU code that use such tracking
to implement its userspace extended quiescent state.
We need to pull this
If we want to stop the tick further idle, we need to be
able to account the cputime without using the tick.
Virtual based cputime accounting solves that problem by
hooking into kernel/user boundaries.
However implementing CONFIG_VIRT_CPU_ACCOUNTING require
to set low level hooks and involves more
Hi,
I'm back on this patchset now that the necessary cputime cleanups are
merged, although more cputime consolidation as in the ctx switch and tick
path should also be done in the future, when I'll get time to cleanup
the s390 part.
So this version of the generic vtime is essentially a rebase aga
Allow to dynamically switch between tick and virtual based cputime accounting.
This way we can provide a kind of "on-demand" virtual based cputime
accounting. In this mode, the kernel will rely on the user hooks
subsystem to dynamically hook on kernel boundaries.
This is in preparation for beeing
Am 03.11.2012 15:14, schrieb Julia Lawall:
> On Sat, 3 Nov 2012, walter harms wrote:
>
>>
>>
>> Am 03.11.2012 11:58, schrieb Julia Lawall:
>>> From: Julia Lawall
>>>
>>> Use WARN rather than printk followed by WARN_ON(1), for conciseness.
>>>
>>> A simplified version of the semantic patch that
> You're guaranteed to be able
> to do this on any Windows 8 certified hardware.
Thats not my understanding of the situation.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel
On 10/29, Ananth N Mavinakayanahalli wrote:
>
> On Fri, Oct 26, 2012 at 06:39:51PM +0200, Oleg Nesterov wrote:
> > >
> > > > OTOH, I do not understand this stuff, everything is nop on x86. And
> > > > when I look into Documentation/cachetlb.txt I am starting to think
> > > > that may be this needs
While looking i have noticed that a lot of drivers define there private
"assert" macro.
It is very similar to warn.
(e.g.)
#define RTL819x_DEBUG
#ifdef RTL819x_DEBUG
#define assert(expr) \
if (!(expr)) { \
printk( "Assertion failed! %s,%s,%
On 11/02/12 22:45, Jeff Moyer wrote:
diff --git a/drivers/scsi/hosts.c b/drivers/scsi/hosts.c
index 593085a..7d7ad8b 100644
--- a/drivers/scsi/hosts.c
+++ b/drivers/scsi/hosts.c
@@ -336,16 +336,25 @@ static struct device_type scsi_host_type = {
**/
struct Scsi_Host *scsi_host_alloc(struct sc
On Fri, 2 Nov 2012, Linus Torvalds wrote:
> On Fri, Nov 2, 2012 at 3:43 PM, Rafael J. Wysocki wrote:
> >
> > Well, not everything is rosy in the suspend land, though. This is a
> > failure to freeze khubd during the second in a row attempt to suspend to
> > RAM (your current tree):
>
> Ugh. So
On 11/02/12 22:45, Jeff Moyer wrote:
diff --git a/drivers/scsi/scsi.c b/drivers/scsi/scsi.c
index 2936b44..4db6973 100644
--- a/drivers/scsi/scsi.c
+++ b/drivers/scsi/scsi.c
@@ -173,16 +173,20 @@ static DEFINE_MUTEX(host_cmd_pool_mutex);
* NULL on failure
*/
static struct scsi_cmnd *
-scs
On 11/02/12 22:45, Jeff Moyer wrote:
Signed-off-by: Jeff Moyer
---
drivers/scsi/sd.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
index 12f6fdf..8deb915 100644
--- a/drivers/scsi/sd.c
+++ b/drivers/scsi/sd.c
@@ -2714,7 +2714,7
On Sat, Nov 3, 2012 at 12:31 PM, Alan Cox wrote:
>> You're guaranteed to be able
>> to do this on any Windows 8 certified hardware.
>
> Thats not my understanding of the situation.
Windows 8 certification has this as a requirement for x86 hardware. I
belied the opposite is a requirement for arm
On Sat, Nov 03, 2012 at 04:31:52PM +, Alan Cox wrote:
> > You're guaranteed to be able
> > to do this on any Windows 8 certified hardware.
>
> Thats not my understanding of the situation.
"17. Mandatory. On non-ARM systems, the platform MUST implement the
ability for a physically present us
On Sat, Nov 03, 2012 at 12:37:44PM -0400, Eric Paris wrote:
> On Sat, Nov 3, 2012 at 12:31 PM, Alan Cox wrote:
> >> You're guaranteed to be able
> >> to do this on any Windows 8 certified hardware.
> >
> > Thats not my understanding of the situation.
>
> Windows 8 certification has this as a requ
On Fri, Nov 2, 2012 at 11:05 PM, Huang Ying wrote:
> On Fri, 2012-11-02 at 10:52 -0600, Bjorn Helgaas wrote:
>> On Wed, Oct 24, 2012 at 12:54 AM, Huang Ying wrote:
>> > Some actions during shutdown need device to be in D0 state, such as
>> > MSI shutdown etc, so resume device before shutdown.
>>
On Fri, Nov 2, 2012 at 11:06 PM, Huang Ying wrote:
> On Fri, 2012-11-02 at 10:50 -0600, Bjorn Helgaas wrote:
>> On Wed, Oct 24, 2012 at 12:54 AM, Huang Ying wrote:
>> > If a PCI device and its parents are put into D3cold, unbinding the
>> > device will trigger deadlock as follow:
>> >
>> > - driv
On Fri, Nov 2, 2012 at 11:29 AM, Greg Kroah-Hartman
wrote:
> On Thu, Nov 01, 2012 at 11:15:52PM -0700, Luca Clementi wrote:
>> Created the module_exit for the android logger so that
>> it can be loaded and unloaded as a module. Fixed
>> module_init and some other minor issues.
>
> That's doing mor
On 11/03/2012 03:03 AM, Sasha Levin wrote:
> On 11/02/2012 12:18 PM, Jiri Slaby wrote:
>> On 11/02/2012 05:07 PM, Sasha Levin wrote:
>>> On Fri, Nov 2, 2012 at 11:51 AM, Jiri Slaby wrote:
On 10/31/2012 04:59 PM, Sasha Levin wrote:
> So you probably want a lot more than 100k syscalls, why
On Sat, Nov 03, 2012 at 11:21:58AM +0100, Daniel Vetter wrote:
>
> Well, we know for sure that fdi link training is broken - it doesn't match
> at all what the spec says we should do. I've been working on this lately,
> since in quite a few circumstances the link train fails without the
> relevent
On 10/31/2012 06:06 AM, Borislav Petkov wrote:
>> Realistically, a single macro could be defined in compiler*.h that
>> encapsulates the entirety of this mechanism and only exposes a "black
>> box" macro, that will simply expand to something that breaks the build
>> in the most appropriate fashion
From: Nicolas Ferre
Date: Tue, 30 Oct 2012 12:30:28 +0100
> Due to the use of common structure in at91_ether and macb drivers,
> change the name of DMA descriptor structures in at91_ether as well:
> dma_desc => macb_dma_desc
>
> Signed-off-by: Nicolas Ferre
This does not apply to net-next, res
From: Xiaotian Feng
Date: Wed, 31 Oct 2012 16:06:01 +0800
> If tasklet_disable() is called before related tasklet handled,
> tasklet_kill will never be finished. tasklet_kill is enough.
>
> Signed-off-by: Xiaotian Feng
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux
From: Xiaotian Feng
Date: Wed, 31 Oct 2012 18:29:57 +0800
> Some driver uses tasklet_disable in device remove/close process,
> tasklet_disable will inc tasklet->count and return. If the tasklet
> is not handled yet because some softirq pressure, the tasklet will
> placed on the tasklet_vec, never
From: Francois Romieu
Date: Thu, 1 Nov 2012 23:21:13 +0100
> Cyril Brulebois :
>> This regression was spotted between Debian squeeze and Debian wheezy
>> kernels (respectively based on 2.6.32 and 3.2). More info about
>> Wake-on-LAN issues with Realtek's 816x chipsets can be found in the
>> foll
From: Masanari Iida
Date: Fri, 2 Nov 2012 23:36:17 +0900
> Correct spelling typo in bnx2x driver
>
> Signed-off-by: Masanari Iida
Applied.
--
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 h
Hi Gururaja,
On Wed, Oct 31, 2012 at 12:39 AM, Hebbar, Gururaja
wrote:
> On Wed, Oct 31, 2012 at 01:58:32, Joel A Fernandes wrote:
>> Hi Gururaja,
>>
>> On Mon, Oct 29, 2012 at 10:45 AM, Hebbar, Gururaja
>> wrote:
>> > Matt,
>> >
>> > On Wed, Oct 10, 2012 at 20:00:49, Porter, Matt wrote:
>> >>
On Sat, Nov 3, 2012 at 1:46 AM, Mika Westerberg
wrote:
> ACPI 5 introduced SPISerialBus resource that allows us to enumerate and
> configure the SPI slave devices behind the SPI controller. This patch adds
> support for this to the SPI core.
>
> In addition we bind ACPI nodes to SPI devices. This
From: Julia Lawall
Date: Sat, 3 Nov 2012 11:58:31 +0100
> From: Julia Lawall
>
> Use WARN rather than printk followed by WARN_ON(1), for conciseness.
>
> A simplified version of the semantic patch that makes this transformation
> is as follows: (http://coccinelle.lip6.fr/)
...
> Signed-off-b
From: Paul Bolle
Date: Sat, 03 Nov 2012 10:53:15 +0100
> Building atp.o triggers this GCC warning:
> drivers/net/ethernet/realtek/atp.c: In function ‘set_rx_mode’:
> drivers/net/ethernet/realtek/atp.c:871:26: warning: ‘mc_filter[0]’ may be
> used uninitialized in this function [-Wuniniti
Hi Linus,
The following changes since commit 08f05c49749ee655bef921d12160960a273aad47:
Return the right error value when dup[23]() newfd argument is too large
(2012-10-30 21:27:28 -0700)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs
From: Julia Lawall
Use WARN(1,...) rather than printk followed by WARN(1).
Signed-off-by: Julia Lawall
---
scripts/coccinelle/misc/warn.cocci | 109 +
1 file changed, 109 insertions(+)
diff --git a/scripts/coccinelle/misc/warn.cocci
b/scripts/coccinelle/
Den 01.11.2012 21:57, skrev Thomas Gleixner:
Dear RT Folks,
I'm pleased to announce the 3.6.5-rt14 release. 3.6.4-rt12 is an
intermediate release with a few changes. 3.6.5-rt13 is an update to
3.6.5 and 3.6.5-rt14 has a fix for my stupidity to release from the
wrong tree missing a fix for x86-32
On Fri, Sep 7, 2012 at 8:04 AM, tip-bot for Suzuki K. Poulose
wrote:
> Reported-by: Ananth N. Mavinakayanahalli
> Signed-off-by: Suzuki K. Poulose
> Acked-by: David Ahern
> Cc: Ananth N Mavinakayanahalli
> Cc: David Ahern
> Cc: Frederic Weisbecker
> Cc: Ingo Molnar
> Cc: Jiri Olsa
> Cc: Na
On Sat, Nov 03, 2012 at 01:42:02PM -0600, Bjorn Helgaas wrote:
> On Sat, Nov 3, 2012 at 1:46 AM, Mika Westerberg
> wrote:
> > ACPI 5 introduced SPISerialBus resource that allows us to enumerate and
> > configure the SPI slave devices behind the SPI controller. This patch adds
> > support for this
On Fri, 2012-09-28 at 11:52 -0700, Greg Kroah-Hartman wrote:
> From: Greg KH
>
> 3.5-stable review patch. If anyone has any objections, please let me know.
Hi Greg,
Can we please apply this patch to the older stable kernels too? I see
that Ben has already applied it to the 3.2 kernel, but it
These patches convert a conditional with a simple test expression and a
then branch that only calls WARN_ON(1) to just a call to WARN_ON, which
will test the condition.
//
@@
expression e;
@@
(
if(<+...e(...)...+>) WARN_ON(1);
|
- if (e) WARN_ON(1);
+ WARN_ON(e);
)//
--
To unsubscribe from thi
From: Julia Lawall
Just use WARN_ON rather than an if containing only WARN_ON(1).
A simplified version of the semantic patch that makes this transformation
is as follows: (http://coccinelle.lip6.fr/)
//
@@
expression e;
@@
- if (e) WARN_ON(1);
+ WARN_ON(e);
//
Signed-off-by: Julia Lawall
-
From: Julia Lawall
Just use WARN_ON rather than an if containing only WARN_ON(1).
A simplified version of the semantic patch that makes this transformation
is as follows: (http://coccinelle.lip6.fr/)
//
@@
expression e;
@@
- if (e) WARN_ON(1);
+ WARN_ON(e);
//
Signed-off-by: Julia Lawall
-
From: Julia Lawall
Just use WARN_ON rather than an if containing only WARN_ON(1).
A simplified version of the semantic patch that makes this transformation
is as follows: (http://coccinelle.lip6.fr/)
//
@@
expression e;
@@
- if (e) WARN_ON(1);
+ WARN_ON(e);
//
Signed-off-by: Julia Lawall
-
From: Julia Lawall
Just use WARN_ON rather than an if containing only WARN_ON(1).
A simplified version of the semantic patch that makes this transformation
is as follows: (http://coccinelle.lip6.fr/)
//
@@
expression e;
@@
- if (e) WARN_ON(1);
+ WARN_ON(e);
//
Signed-off-by: Julia Lawall
-
From: Julia Lawall
Just use WARN_ON rather than an if containing only WARN_ON(1).
A simplified version of the semantic patch that makes this transformation
is as follows: (http://coccinelle.lip6.fr/)
//
@@
expression e;
@@
- if (e) WARN_ON(1);
+ WARN_ON(e);
//
Signed-off-by: Julia Lawall
-
From: Julia Lawall
Just use WARN_ON rather than an if containing only WARN_ON(1).
A simplified version of the semantic patch that makes this transformation
is as follows: (http://coccinelle.lip6.fr/)
//
@@
expression e;
@@
- if (e) WARN_ON(1);
+ WARN_ON(e);
//
Signed-off-by: Julia Lawall
-
From: Julia Lawall
Just use WARN_ON rather than an if containing only WARN_ON(1).
A simplified version of the semantic patch that makes this transformation
is as follows: (http://coccinelle.lip6.fr/)
//
@@
expression e;
@@
- if (e) WARN_ON(1);
+ WARN_ON(e);
//
Signed-off-by: Julia Lawall
-
From: Julia Lawall
Just use WARN_ON rather than an if containing only WARN_ON(1).
A simplified version of the semantic patch that makes this transformation
is as follows: (http://coccinelle.lip6.fr/)
//
@@
expression e;
@@
- if (e) WARN_ON(1);
+ WARN_ON(e);
//
Signed-off-by: Julia Lawall
-
On Saturday, November 03, 2012 01:42:02 PM Bjorn Helgaas wrote:
> On Sat, Nov 3, 2012 at 1:46 AM, Mika Westerberg
> wrote:
> > ACPI 5 introduced SPISerialBus resource that allows us to enumerate and
> > configure the SPI slave devices behind the SPI controller. This patch adds
> > support for this
On Saturday, November 03, 2012 10:13:10 PM Mika Westerberg wrote:
> On Sat, Nov 03, 2012 at 01:42:02PM -0600, Bjorn Helgaas wrote:
> > On Sat, Nov 3, 2012 at 1:46 AM, Mika Westerberg
> > wrote:
> > > ACPI 5 introduced SPISerialBus resource that allows us to enumerate and
> > > configure the SPI sl
From: Jan H. Schönherr
The meaning of LOG_CONT is unclear, i. e., whether a message is a starting,
ending, or middle fragment. Unfortunately, this cannot be inferred from
the LOG_PREFIX and LOG_NEWLINE flags, as they are not always kept.
Furthermore, in some cases LOG_CONT is set, although it is
On Tue, Oct 30, 2012 at 7:47 AM, Yinghai Lu wrote:
> On Tue, Oct 30, 2012 at 6:44 AM, Konrad Rzeszutek Wilk
> wrote:
>> On Wed, Oct 10, 2012 at 11:13:45PM -0700, Yinghai Lu wrote:
>> So which branch should I try out? Do you have one with all of the
>> required patches so I can just do a 3.7-rc3 '
I am travelling at the moment... I hope to be able to look at it Sunday.
Yinghai Lu wrote:
>On Tue, Oct 30, 2012 at 7:47 AM, Yinghai Lu wrote:
>> On Tue, Oct 30, 2012 at 6:44 AM, Konrad Rzeszutek Wilk
>> wrote:
>>> On Wed, Oct 10, 2012 at 11:13:45PM -0700, Yinghai Lu wrote:
>>> So which branch
On Sat, 3 Nov 2012 09:46:33 +0200, Mika Westerberg wrote:
> ACPI 5 introduced I2cSerialBus resource that makes it possible to enumerate
> and configure the I2C slave devices behind the I2C controller. This patch
> adds helper functions to support I2C slave enumeration.
>
> An ACPI enabled I2C con
This patch-set is the result of fixing some problems encountered when
building the kernel with randconfig and a when running a script I wrote
to identify unused structures.
arch/arm/mach-at91/at91sam9263_devices.c | 20
arch/arm/mach-integrator/cpu.c | 12 --
Since unthrottle_offline_cfs_rqs is only ever invoked when CONFIG_SMP
let's pre-processor it out when SMP is not configured. This change
suppresses the build error below when !CONFIG_SMP.
kernel/sched/fair.c:2055:13: warning: ‘unthrottle_offline_cfs_rqs’ defined but
not used [-Wunused-function]
This patch fixes:
drivers/isdn/i4l/isdn_common.c: In function ‘isdn_ioctl’:
drivers/isdn/i4l/isdn_common.c:1278:8: warning: unused variable ‘s’
[-Wunused-variable]
Cc: Karsten Keil
Cc: net...@vger.kernel.org
Signed-off-by: Lee Jones
---
drivers/isdn/i4l/isdn_common.c |1 -
1 file changed,
This was introduced way back before 2005 and has remained unused for
over 7 years. Let's remove it.
Cc: Russell King
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Lee Jones
---
arch/arm/mach-integrator/cpu.c | 12
1 file changed, 12 deletions(-)
diff --git a/arch/arm/m
This the at91sam9g45_isi_device structure and its associated resources
were added in 2008 and have been unused ever since. Let's remove them.
Cc: Russell King
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Lee Jones
---
arch/arm/mach-at91/at91sam9263_devices.c | 20 --
Instead of issuing (0) statements when !CONFIG_SYSFS which will cause
'warning: ', we'll use inline statements instead. This will effectively
do the same thing, but suppress any unnecessary warnings.
Cc: Stephen Hemminger
Cc: bri...@lists.linux-foundation.org
Cc: net...@vger.kernel.org
Signed-off
quotactl_cmd_write() is only ever invoked when BLOCK is configured. When
!CONFIG_BLOCK, the build warning below is displayed. Let's fix that.
fs/quota/quota.c:311:12: warning: ‘quotactl_cmd_write’ defined but not used
[-Wunused-function]
Cc: Jan Kara
Signed-off-by: Lee Jones
---
fs/quota/quot
drivers/virtio/virtio_mmio.c: In function ‘vm_cmdline_set’:
drivers/virtio/virtio_mmio.c:535:4: warning: format ‘%u’ expects argument of
type ‘unsigned int *’, but argument 4 has type ‘resource_size_t *’ [-Wformat]
Cc: Rusty Russell
Cc: virtualizat...@lists.linux-foundation.org
Signed-off-by: Le
If !CONFIG_SPI and !CONFIG_I2C* then there is no point adding support
for the adav80x codec as it relies on a bus to operate. This patch
fixes the build warnings below when SPI and I2C are not specified in
the configuration.
sound/soc/codecs/adav80x.c:842:22: warning: ‘adav80x_bus_probe’ defined b
arch/x86/kernel/quirks.c: In function ‘ati_force_enable_hpet’:
arch/x86/kernel/quirks.c:364:4: warning: ‘d’ may be used uninitialised in this
function [-Wuninitialized]
arch/x86/kernel/quirks.c:357:6: note: ‘d’ was declared here
arch/x86/kernel/quirks.c:407:21: warning: ‘val’ may be used uninitial
On Saturday 03 November 2012 12:58:45 Shan Wei wrote:
> Sven Eckelmann said, at 2012/11/3 1:55:
> > On Saturday 03 November 2012 00:02:06 Shan Wei wrote:
> >> From: Shan Wei
> >>
> >> As Christoph Lameter said:
> >>> In addition, following usage of per_cpu_ptr can be replaced by
> >>> this_cpu_re
On Sat, 2012-11-03 at 23:02 +0100, Lee Jones wrote:
> This patch fixes:
> drivers/isdn/i4l/isdn_common.c: In function ‘isdn_ioctl’:
> drivers/isdn/i4l/isdn_common.c:1278:8: warning: unused variable ‘s’
> [-Wunused-variable]
Did you have CONFIG_NETDEVICES not set in this build?
Paul Bolle
--
To
On Sat, 03 Nov 2012, Paul Bolle wrote:
> On Sat, 2012-11-03 at 23:02 +0100, Lee Jones wrote:
> > This patch fixes:
> > drivers/isdn/i4l/isdn_common.c: In function ‘isdn_ioctl’:
> > drivers/isdn/i4l/isdn_common.c:1278:8: warning: unused variable ‘s’
> > [-Wunused-variable]
>
> Did you have CONFIG
On Sat, 2012-11-03 at 13:46 +, Matthew Garrett wrote:
> On Sat, Nov 03, 2012 at 12:03:56PM +, James Bottomley wrote:
> > On Sat, 2012-11-03 at 00:22 +, Matthew Garrett wrote:
> > > Why would an attacker use one of those Linux systems? There's going to
> > > be plenty available that don
dma-debug depends on get_dma_ops() interface. Several architectures
do not define dma_ops and get_dma_ops(). When dma debug interfaces are
used on an architecture (e.g: c6x) that doesn't define get_dmap_ops(),
compilation fails. Changing dma-debug to call dma_mapping_error() instead
of defining its
not sure what/where this is coming from.. seen this a few times already.
[16870.135447] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[16870.135448] cfg80211: (549 KHz - 560 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[16870.135449] cfg80211: (565 KHz - 5710
On 11/03/2012 11:55 AM, Jiri Slaby wrote:
> On 11/03/2012 03:03 AM, Sasha Levin wrote:
>> On 11/02/2012 12:18 PM, Jiri Slaby wrote:
>>> On 11/02/2012 05:07 PM, Sasha Levin wrote:
On Fri, Nov 2, 2012 at 11:51 AM, Jiri Slaby wrote:
> On 10/31/2012 04:59 PM, Sasha Levin wrote:
>> So you
On Fri, 2 Nov 2012, Vivek Goyal wrote:
> > With secure boot enabled, then the kernel should refuse to let an
> > unsigned kexec load new images, and kexec itself should refuse to
> > load unsigned images.
>
> Yep, good in theory. Now that basically means reimplementing kexec-tools
> in kernel.
Fixed coding style issues.
---
drivers/staging/rtl8187se/r8185b_init.c | 57 ---
1 file changed, 30 insertions(+), 27 deletions(-)
diff --git a/drivers/staging/rtl8187se/r8185b_init.c
b/drivers/staging/rtl8187se/r8185b_init.c
index bf34319..da4f592 100644
--- a/driv
101 - 200 of 228 matches
Mail list logo
