If p54u_load_firmware() fails, p54u_probe() does not deallocate
already allocated resources. The patch adds proper failure handling.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/net/wireless/p54/p54usb.c | 4
1 file changed, 4
On Fri, 7 Mar 2014 11:58:52 +0900 Minchan Kim wrote:
> On Thu, Mar 06, 2014 at 10:21:32AM -0800, Laura Abbott wrote:
> > We received several reports of bad page state when freeing CMA pages
> > previously allocated with alloc_contig_range:
> >
> > <1>[ 1258.084111] BUG: Bad page state in process
From: David Howells
Date: Thu, 06 Mar 2014 22:31:18 +
> David Miller wrote:
>
>> It depends upon whether you want the bug fixes to go into Linus's
>> tree for the current release or not.
>
> The fixes aren't particularly urgent, so if net-next is aimed at the next
> merge window, I would b
Dave,
Please pull this batch of fixes intende for the 3.14 stream...
For the mac80211 bits, Johannes says:
"Here I have a fix from Eliad for the minimal channel width calculation
in the mac80211 code which lead to monitor mode not working at all for
drivers using that. One of my fixes is for an
On 03/07/2014 11:39 AM, Don Zickus wrote:
> A customer generated an external NMI using their iLO to test kdump worked.
> Unfortunately, the machine hung. Disabling the nmi_watchdog made things work.
>
> I speculated the external NMI fired, caused the machine to panic (as expected)
> and the perf
From: Joe Perches
Date: Fri, 07 Mar 2014 13:02:44 -0800
> Right now, checkpatch emits a --strict only warning on "&&" or "||"
> at the beginning of line but that could be changed to any "$Operators"
>
> our $Arithmetic = qr{\+|-|\*|\/|%};
> our $Operators= qr{
> <=|
On Fri, 7 Mar 2014 10:58:43 +0800 Liu ShuoX wrote:
>
> ftrace_read_cnt need to be reset in open to support mutli times
> getting the records.
>
> Signed-off-by: Liu ShuoX
> ---
> fs/pstore/ram.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/pstore/ram.c b/fs
On Fri, 7 Mar 2014 22:00:51 +0100
Jean Delvare wrote:
> As far as I know, the CS5535 and CS5536 chipsets are companions of the
> Geode series of processors, which are 32-bit only. So the CS5535
> drivers are not needed on x86-64, except for build testing purpose.
>
> This aligns the dependencies
From: Hayes Wang
Date: Fri, 7 Mar 2014 11:04:33 +0800
> - Select the suitable spin lock for each function.
> - Add additional check to reduce the spin lock.
> - Up the priority of the tx to avoid interrupted by rx.
> - Support rx checksum, large send, and IPv6 hw checksum.
Series applied, th
On Saturday, March 08, 2014 01:11:49 AM Alexey Khoroshilov wrote:
> If p54u_load_firmware() fails, p54u_probe() does not deallocate
> already allocated resources. The patch adds proper failure handling.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey K
On Fri, 7 Mar 2014 11:13:27 -0800
Soren Brinkmann wrote:
> Signed-off-by: Soren Brinkmann
> ---
> drivers/tty/serial/xilinx_uartps.c | 6 +-
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/drivers/tty/serial/xilinx_uartps.c
> b/drivers/tty/serial/xilinx_uartps.c
> index
On Fri, 7 Mar 2014 11:13:29 -0800
Soren Brinkmann wrote:
> Signed-off-by: Soren Brinkmann
> ---
> I'm not sure about this change. Is this acceptable or already too much?
> I think the name is used for some sysfs entries.
Its probably not a good idea. You might be ok depending whether anything
On Fri, Mar 07, 2014 at 01:02:44PM -0800, Joe Perches wrote:
> On Fri, 2014-03-07 at 15:41 -0500, David Miller wrote:
> > From: Alistair Popple
> > Date: Thu, 6 Mar 2014 14:52:25 +1100
> >
> > > + out_be32(dev->reg, in_be32(dev->reg) | WKUP_ETH_RGMIIEN
> > > + | WKUP_ETH_TX_OE | WKUP_ET
On Fri, 7 Mar 2014 11:13:31 -0800
Soren Brinkmann wrote:
> Rename the config symbols for the Cadence UART to reflect the driver
> rebranding:
> SERIAL_XILINX_PS_UART(_CONSOLE) -> SERIAL_CADENCE_UART(_CONSOLE)
This breaks all those setups people have with pre-packed .config files
that have wor
On Sat, Mar 08, 2014 at 01:48:42AM +0530, Nilesh More wrote:
>
> 1. When the USB is hotplugged, in the call stack of add_disk( ),
> while registering disk blkdev_get(bdev, FMODE_READ, NULL) gets called
> which I guess scans the partition table, initializes part array and
> registers the partitions
From: Jason Wang
Date: Fri, 7 Mar 2014 13:28:27 +0800
> This is because the delay added by htb may lead the delay the finish
> of DMAs and cause the pending DMAs for tap0 exceeds the limit
> (VHOST_MAX_PEND). In this case vhost stop handling tx request until
> htb send some packets. The problem
+ Paolo.
(drop Andreas' old, invalid now email).
On Fri, Mar 07, 2014 at 01:01:22PM -0800, H. Peter Anvin wrote:
> > qemu64 triggers this ? That spew comes from amd_k7_smp_check()
> > which should only run on family 6, which was all 32bit.
>
> [0.152749] smpboot: CPU0: AMD QEMU Virtual CPU
On Thu, 6 Mar 2014 18:23:39 +0100
Andrew Lunn wrote:
> > Can't we fix this so the probe order doesn't affect the name?
> >
> > Is that sane?
>
> You are not supposed to trust the device name, since probing can
> happen in parallel, on different buses. udev should have rules to name
> the interf
On Fri, 2014-03-07 at 13:30 -0800, j...@joshtriplett.org wrote:
> On Fri, Mar 07, 2014 at 01:02:44PM -0800, Joe Perches wrote:
> > On Fri, 2014-03-07 at 15:41 -0500, David Miller wrote:
> > > From: Alistair Popple
> > > Date: Thu, 6 Mar 2014 14:52:25 +1100
> > >
> > > > + out_be32(dev->reg
From: "K. Y. Srinivasan"
Date: Thu, 6 Mar 2014 21:32:36 -0800
> +static u32 fill_pg_buf(struct page *page, u32 offset, u32 len,
> + struct hv_page_buffer *pb)
> +{
> + int j = 0;
> +
> + /* Deal with compund pages by ignoring unused part
> + * of the page.
> +
-statfs(2) /undefined
-Don't recalculate f_frsize and f_bavail.
-Remove ?? comment.
-Use defined CEPH_BLOCK.
-Directly work with >> 12 for 4Kb conversions (like in dir.c)
Signed-off-by: Fabian Frederick
---
fs/ceph/super.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
dif
Am Freitag, den 07.03.2014, 10:56 -0800 schrieb Andy Lutomirski:
> On Thu, Mar 6, 2014 at 11:21 PM, Stefani Seibold wrote:
> > Hi Fengguang,
> >
> > i have build a kernel with the config, but my kvm is unable to start it.
> > I will try to find a way to test your kernek config.
> >
> > One thing
Hello,I know this mail seems you in a good form,lets see what future has in
store,please contact me soonest marisa_...@yahoo.com Thanks marisa
--
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 ht
> - The renderer supports *any* RGB target, from 8bit to 32bit with
>big-endian and little-endian support. The related pixel-renderer will
>probably never win a beauty-contest, but it works.. Again, who cares
>for debug-log rendering speed?
Debug log writing performance is extremely i
On 2014-03-07 21:55, Guenter Roeck wrote:
On Fri, Mar 07, 2014 at 08:33:02PM +0100, Manuel Krause wrote:
Please have a short look at the following BUG report + the comments
-- this message here is a kind of FWD-ing it:
https://bugs.archlinux.org/task/39005
I came late to test kernel 3.13 with t
On Fri, Mar 07, 2014 at 10:38:56PM +0100, Borislav Petkov wrote:
> * Another option would be if we change the f/m/s of "qemu64" so that
> the test doesn't fire.
>
> What also makes me wonder is why is this thing even called qemu64?? AMD
> family 6 was 32-bit only CPUs so 64 is kinda wrong IM
On Fri, Mar 7, 2014 at 2:03 PM, Paul Bolle wrote:
> On Fri, 2014-03-07 at 13:40 -0700, Bjorn Helgaas wrote:
>> It seems quite possible that I broke pci_bus_alloc_resource(), which could
>> cause an allocation failure like this.
>>
>> If you have a chance to try it, here's a debug patch against v3.
Fully agree.
It will be a very helpful feature to make ple setting per VM.
This feature will provide more flexible control to the VM user. All KVM user
will love to have it.
The enhancement we proposed is neither overlapping nor conflicting with this
feature. The enhancement is targeting to pro
On 03/07/2014 02:06 PM, Dave Jones wrote:
> On Fri, Mar 07, 2014 at 10:38:56PM +0100, Borislav Petkov wrote:
>
> > * Another option would be if we change the f/m/s of "qemu64" so that
> > the test doesn't fire.
> >
> > What also makes me wonder is why is this thing even called qemu64?? AMD
>
On Fri, Mar 7, 2014 at 12:38 PM, David Miller wrote:
> From: Alexei Starovoitov
> Date: Wed, 5 Mar 2014 19:30:15 -0800
>
>> Extended BPF extends old BPF in the following ways:
>> - from 2 to 10 registers
>> Original BPF has two registers (A and X) and hidden frame pointer.
>> Extended BPF ha
On Fri, Mar 07, 2014 at 05:06:55PM -0500, Dave Jones wrote:
> Additionally, fam:6 model:6 stepping 3 never existed in the real
> world afaict. I used to keep x86info's stepping db pretty up to date,
> and that only has knowledge of stepping 1 & 2.[*] Modelling qemu on
> something from the real worl
On Fri, Mar 07, 2014 at 02:11:50PM -0800, H. Peter Anvin wrote:
> > > * Another option would be if we change the f/m/s of "qemu64" so that
> > > the test doesn't fire.
> > >
> > > What also makes me wonder is why is this thing even called qemu64?? AMD
> > > family 6 was 32-bit only CPU
Hi Andy,
Thanks for the patch.
> +#define BAM_IRQ_SRCS_EE(pipe)(0x0800 + ((pipe) * 0x80))
> +#define BAM_IRQ_SRCS_MSK_EE(pipe)(0x0804 + ((pipe) * 0x80))
s/pipe/ee ?
> +struct bam_chan {
> + struct virt_dma_chan vc;
> +
> + struct bam_device *bdev;
> +
> + /*
On Fri, Mar 07, 2014 at 02:11:50PM -0800, H. Peter Anvin wrote:
> On 03/07/2014 02:06 PM, Dave Jones wrote:
> > On Fri, Mar 07, 2014 at 10:38:56PM +0100, Borislav Petkov wrote:
> >
> > > * Another option would be if we change the f/m/s of "qemu64" so that
> > > the test doesn't fire.
> > >
> >
On Fri, Mar 07, 2014 at 11:20:18PM +0100, Borislav Petkov wrote:
> Yeah, I think the test in the kernel is open above as a precaution in
> case newer models appeared:
>
> if (((c->x86_model == 6) && (c->x86_mask >= 2)) ||
>
> I hardly can imagine, though, if anyone is actually boo
On Sat, Mar 08, 2014 at 06:27:50AM +0800, Fengguang Wu wrote:
> Yeah I confirmed that it works w/o the warning!
>
> [0.575854] smpboot: CPU0: Intel Core Processor (Haswell) (fam: 06, model:
> 3c, stepping: 01)
Hahah, Haswell is just a couple models away from K7: model 6 vs
model 3c, same fam
On 6.3.2014 19:21, Laura Abbott wrote:
We received several reports of bad page state when freeing CMA pages
previously allocated with alloc_contig_range:
<1>[ 1258.084111] BUG: Bad page state in process Binder_A pfn:63202
<1>[ 1258.089763] page:d21130b0 count:0 mapcount:1 mapping: (null)
inde
On Fri, Mar 07, 2014 at 05:27:43PM -0500, Dave Jones wrote:
> When I wrote it 10 years or so back it made more sense than it
> probably does now, so I'd be ok with just dropping it all too tbh.
> Machines of that vintage probably have bigger problems now anyway.
Yeah.
> I don't recall seeing a re
From: Borislav Petkov
The name in struct bootparam is ->initrd_addr_max and not ramdisk_max.
Fix that.
Signed-off-by: Borislav Petkov
---
Documentation/x86/boot.txt | 4 ++--
arch/x86/boot/header.S | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/x86/boo
On 7.3.2014 1:33, Andrew Morton wrote:
On Thu, 6 Mar 2014 10:21:32 -0800 Laura Abbott wrote:
We received several reports of bad page state when freeing CMA pages
previously allocated with alloc_contig_range:
<1>[ 1258.084111] BUG: Bad page state in process Binder_A pfn:63202
<1>[ 1258.08976
As usual Eric, your commentary is anything but useful. However your
technical thoughts are not off the mark. Can we stick to those?
On Wed, 2014-03-05 at 10:06 -0800, Eric W. Biederman wrote:
> Steve Grubb writes:
>
> > On Tuesday, March 04, 2014 07:21:52 PM David Miller wrote:
> >> From: ebie
On Fri, Mar 07, 2014 at 11:04:29PM +0100, Manuel Krause wrote:
> On 2014-03-07 21:55, Guenter Roeck wrote:
> >On Fri, Mar 07, 2014 at 08:33:02PM +0100, Manuel Krause wrote:
> >>Please have a short look at the following BUG report + the comments
> >>-- this message here is a kind of FWD-ing it:
> >>
On Fri, Mar 07, 2014 at 01:15:35PM -0800, H. Peter Anvin wrote:
> On 03/07/2014 11:39 AM, Don Zickus wrote:
> > A customer generated an external NMI using their iLO to test kdump worked.
> > Unfortunately, the machine hung. Disabling the nmi_watchdog made things
> > work.
> >
> > I speculated th
On Fri, 2014-03-07 at 09:29PM +, One Thousand Gnomes wrote:
> On Fri, 7 Mar 2014 11:13:29 -0800
> Soren Brinkmann wrote:
>
> > Signed-off-by: Soren Brinkmann
> > ---
> > I'm not sure about this change. Is this acceptable or already too much?
> > I think the name is used for some sysfs entri
On Fri, 2014-03-07 at 09:30PM +, One Thousand Gnomes wrote:
> On Fri, 7 Mar 2014 11:13:31 -0800
> Soren Brinkmann wrote:
>
> > Rename the config symbols for the Cadence UART to reflect the driver
> > rebranding:
> > SERIAL_XILINX_PS_UART(_CONSOLE) -> SERIAL_CADENCE_UART(_CONSOLE)
>
> This
On Fri, Mar 07, 2014 at 01:30:17PM -0800, j...@joshtriplett.org wrote:
> On Fri, Mar 07, 2014 at 01:02:44PM -0800, Joe Perches wrote:
> > On Fri, 2014-03-07 at 15:41 -0500, David Miller wrote:
> > > From: Alistair Popple
> > > Date: Thu, 6 Mar 2014 14:52:25 +1100
> > >
> > > > + out_be32(d
On Fri, Mar 7, 2014 at 1:53 PM, Stefani Seibold wrote:
>
> Am Freitag, den 07.03.2014, 10:56 -0800 schrieb Andy Lutomirski:
>> On Thu, Mar 6, 2014 at 11:21 PM, Stefani Seibold wrote:
>> > Hi Fengguang,
>> >
>> > i have build a kernel with the config, but my kvm is unable to start it.
>> > I will
Commit-ID: d4078e232267ff53f3b030b9698a3c001db4dbec
Gitweb: http://git.kernel.org/tip/d4078e232267ff53f3b030b9698a3c001db4dbec
Author: Peter Zijlstra
AuthorDate: Wed, 5 Mar 2014 14:07:49 +0100
Committer: H. Peter Anvin
CommitDate: Thu, 6 Mar 2014 10:58:18 -0800
x86, trace: Further robu
On Sat, Mar 08, 2014 at 12:29:49AM +0200, Stanimir Vabanov wrote:
> > +#define BAM_IRQ_SRCS_EE(pipe) (0x0800 + ((pipe) * 0x80))
> > +#define BAM_IRQ_SRCS_MSK_EE(pipe) (0x0804 + ((pipe) * 0x80))
>
> s/pipe/ee ?
>
Ah good catch. I'll fix that.
> > +struct bam_chan {
> > + struct
On 02/26, Lorenzo Pieralisi wrote:
> On Tue, Feb 25, 2014 at 08:48:38PM +, Kumar Gala wrote:
> >
> > On Feb 25, 2014, at 5:16 AM, Lorenzo Pieralisi
> > wrote:
> > >
> > > As I mentioned, I do not like the idea of adding compatible properties
> > > just to force the kernel to create platform
On Fri, 2014-03-07 at 09:28PM +, One Thousand Gnomes wrote:
> On Fri, 7 Mar 2014 11:13:27 -0800
> Soren Brinkmann wrote:
>
> > Signed-off-by: Soren Brinkmann
> > ---
> > drivers/tty/serial/xilinx_uartps.c | 6 +-
> > 1 file changed, 1 insertion(+), 5 deletions(-)
> >
> > diff --git a/
On Mon, Mar 03, 2014 at 09:38:03AM +, Shevchenko, Andriy wrote:
> > + if (IS_ERR(bdev->bamclk))
> > + return PTR_ERR(bdev->bamclk);
> > +
> > + ret = clk_prepare_enable(bdev->bamclk);
> > + if (ret) {
> > + dev_err(bdev->dev, "failed to prepare/enable clock\n");
> >
Hi
On Fri, Mar 7, 2014 at 10:58 PM, One Thousand Gnomes
wrote:
>> - The renderer supports *any* RGB target, from 8bit to 32bit with
>>big-endian and little-endian support. The related pixel-renderer will
>>probably never win a beauty-contest, but it works.. Again, who cares
>>for deb
On 03/07/2014 08:06 AM, Stefani Seibold wrote:
>>
>> wfg@bee /tmp% git clone --reference /c/linux
>> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
>
> As i wrote i already cloned the tip tree!!
>
> But i cannot see the changeset, there is also no VDSO changes set in the
> git log
On Sat, 2014-03-08 at 02:04 +0300, Dan Carpenter wrote:
> On Fri, Mar 07, 2014 at 01:30:17PM -0800, j...@joshtriplett.org wrote:
> > On Fri, Mar 07, 2014 at 01:02:44PM -0800, Joe Perches wrote:
> > > On Fri, 2014-03-07 at 15:41 -0500, David Miller wrote:
> > > > From: Alistair Popple
> > > > Date:
Commit-ID: 5fa10196bdb5f190f595ebd048490ee52dddea0f
Gitweb: http://git.kernel.org/tip/5fa10196bdb5f190f595ebd048490ee52dddea0f
Author: H. Peter Anvin
AuthorDate: Fri, 7 Mar 2014 15:05:20 -0800
Committer: H. Peter Anvin
CommitDate: Fri, 7 Mar 2014 15:08:14 -0800
x86: Ignore NMIs that co
On Fri, 2014-03-07 at 11:13AM -0800, Soren Brinkmann wrote:
> The Xilinx UARTPS driver has been renamed to Cadence UART. Remove
> the stale Xilinx UARTPS config options and add Cadence UART instead.
This will also be dropped, since the corresponding renaming of config
symbol gets dropped.
Hi Suresh,
Any thoughts on this?
-hpa
On 02/27/2014 03:44 PM, H. Peter Anvin wrote:
> So, picking up this thread which got dropped on the floor...
>
> On 02/01/2014 11:19 PM, Suresh Siddha wrote:
>>
>> diff --git a/arch/x86/kernel/i387.c b/arch/x86/kernel/i387.c
>> index e8368c6..4e5f77
Placeholders <..> are sometimes used in the devicetree documentation
to define family-wide compatible strings (like fsl,-ipu where
chip can be any Freescale SoC).
These placeholders are loosly defined. This lead to some
fragmentation. Looking at the current placeholders, we have:
3
32
Hi Linus,
A small collection of minor fixes. The FPU stuff is still pending, I
fear. I haven't heard anything from Suresh so I suspect I'm going to
have to dig into the init specifics myself and fix up the patchset.
The following changes since commit 0414855fdc4a40da05221fc6062cccbc0c30f169:
Improve the vendor name match in vendor-prefix.txt
by only matching the exact vendor name at the beginning of lines.
Signed-off-by: Florian Vaussard
---
scripts/checkpatch.pl | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch
Look for ".compatible = "foo" strings not only in .dts files, but
in .c and .h too.
Signed-off-by: Florian Vaussard
---
scripts/checkpatch.pl | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 96f10ba..9205153 100755
---
Hi,
This series proposes a number of fixes and enhancements to the checks
performed on compatible strings:
1) Fix vendor check for strings with dashes
2) Fix spurious vendor warning, when there is no vendor
3) Check for compatible strings in .c and .h files too
4) Match only at the begining of ea
The current vendor compatible check will not match vendors with
dashes, like:
compatible="asahi-kasei"
Reported-by: Joe Perches
Signed-off-by: Florian Vaussard
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpat
With a compatible string like
compatible = "foo";
checkpatch will currently try to find "foo" in vendor-prefixes.txt,
which is wrong since the vendor prefix is empty in this specific case.
Skip the vendor test if the compatible is not like
compatible = "vendor,something";
Signed-off-by: Flori
Hi Stefani,
> So i tried my best, but without support it is impossible to find all
> issues. But mostly what i get was bureaucracy afflictions
>
> I complied, but now it is time to help finding the issues. And not only
> do a complain, sit back and wait.
I feel sorry if that's what you perceived
On 7 Mar 2014 at 11:08, beh...@converseincode.com wrote:
> diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h
> index c3eb102..5ce1f67 100644
> --- a/include/linux/moduleparam.h
> +++ b/include/linux/moduleparam.h
> @@ -346,6 +346,7 @@ static inline void destroy_params(const st
On Fri, 2014-03-07 at 11:13AM -0800, Soren Brinkmann wrote:
> Use 'CDNS_UART' or 'cdns_uart' instead of 'XUARTPS' and 'xuartps' as
> function and symbol prefix. This is essentially doing:
> - s/XUARTPS/CDNS_UART/g
> - s/xuartps/cdns_uart/g
> The only exception is PORT_XUARTPS, which stays as is,
Hi Steven,
At Sun, 02 Mar 2014 21:20:31 +0900,
Satoru Takeuchi wrote:
>
> From: Satoru Takeuchi
>
> If we'd like to set the redirect target file of run_command(),
> we should define $redirect before calling this function and should undef it
> after calling this function. Since it's user-unfrien
On Fri, Mar 7, 2014 at 1:25 PM, Andrew Morton wrote:
> On Fri, 7 Mar 2014 10:58:43 +0800 Liu ShuoX wrote:
>
>>
>> ftrace_read_cnt need to be reset in open to support mutli times
>> getting the records.
>>
>> Signed-off-by: Liu ShuoX
>> ---
>> fs/pstore/ram.c | 3 ++-
>> 1 file changed, 2 inse
On Fri, 2014-03-07 at 09:15 -0800, Dave Hansen wrote:
> On 03/06/2014 05:55 PM, Davidlohr Bueso wrote:
> > On Wed, 2014-03-05 at 16:45 -0800, Dave Hansen wrote:
> >> From: Dave Hansen
> >>
> >> Now that we have some shiny new tracepoints, we can actually
> >> figure out what the heck is going on.
Looks like this is unintentional as the
result = EEH_STATE_UNAVAILABLE is being
overwritten by EEH_STATE_NOT_SUPPORT in the
fallthrough to the default case.
---
diff --git a/arch/powerpc/platforms/pseries/eeh_pseries.c
b/arch/powerpc/platforms/pseries/eeh_pseries.c
index 8a8f047..83da53f 100644
--
Hi Greg,
Here's my pull request for v3.15 merge window.
This pull request contains patches which have been soaking in linux-next for
quite a bit of time. I also ran everything through my 150 randconfigs script
(which uses some seeds of my own).
Please, consider merging it on top of your greg/usb
>On Friday, March 7, 2014 11:38 AM, Hartley Sweeten
> wrote:
>>On Friday, March 07, 2014 1:38 AM, Chase Southwood wrote:
>>This patch fixes the register map defines for the counter registers such
>>that they are all the real offsets to each register, rather than a mix of
>>real offsets and adders
This patch fixes the register map defines for the digital input registers
such that they are all the real offsets to each register, rather than a
mix of real offsets and adders to those offsets.
Further, some of the old defines were being used incorrectly in the
i_APCI1564_Reset() function. Upon
This patch for fixes the register map defines for the watchdog registers
such that they are all the real offsets to each register, rather than a
mix of real offsets and adders to those offsets.
Signed-off-by: Chase Southwood
---
2: Simplified commit message, fixed indentation and whitespace dama
This patch for fixes the register map defines for the timer registers such
that they are all the real offsets to each register, rather than a mix of
real offsets and adders to those offsets.
Signed-off-by: Chase Southwood
---
2: Simplified commit message, fixed indentation and whitespace damage.
This patch fixes the register map defines for the counter registers such
that they are all the real offsets to each register, rather than a mix of
real offsets and adders to those offsets.
Signed-off-by: Chase Southwood
---
2: Simplified commit message, fixed indentation and whitespace damage.
I
This patch fixes the register map defines for the digital output registers
such that they are all the real offsets to each register, rather than a
mix of real offsets and adders to those offsets.
Further, some of the old defines were being used incorrectly in the
i_APCI1564_Reset() function. Upon
On Sat, 08 Mar 2014 09:12:31 +0900
Satoru Takeuchi wrote:
> Hi Steven,
>
> At Sun, 02 Mar 2014 21:20:31 +0900,
> Satoru Takeuchi wrote:
> >
> > From: Satoru Takeuchi
> >
> > If we'd like to set the redirect target file of run_command(),
> > we should define $redirect before calling this funct
From: Eric Paris
Date: Fri, 07 Mar 2014 17:52:02 -0500
> Audit is non-tolerant to failure and loss.
Netlink is not a loss-less transport.
--
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:
On 03/07/14 14:56, PaX Team wrote:
On 7 Mar 2014 at 11:08, beh...@converseincode.com wrote:
diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h
index c3eb102..5ce1f67 100644
--- a/include/linux/moduleparam.h
+++ b/include/linux/moduleparam.h
@@ -346,6 +346,7 @@ static inline
On Friday, March 07, 2014 5:42 PM, Chase Southwood wrote:
>
> This patch fixes the register map defines for the digital input registers
> such that they are all the real offsets to each register, rather than a
> mix of real offsets and adders to those offsets.
>
> Further, some of the old defines w
Handles 0-based per_cpu variables as being absolute so they are
not relocated under kASLR on x86_64.
-Kees
--
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.org/majordomo-info
This refactors the address range checks to be generalized instead of
specific to text range checks, in preparation for other range checks.
Also extracts logic for "is the symbol absolute" into a function.
Signed-off-by: Kees Cook
---
v2:
- return which range entry index an address was found in.
This forces the entire per_cpu range to be reported as absolute
without losing their linker symbol types, when the per_cpu area is
0-based. Without this, the variables are incorrectly shown as relocated
under kASLR on x86_64.
Several kallsyms output in different boot states for comparison of
vario
[+cc Rafael]
On Fri, Mar 07, 2014 at 11:39:48AM -0800, Yinghai Lu wrote:
> On Fri, Mar 7, 2014 at 8:45 AM, Bjorn Helgaas wrote:
> >
> > I opened a bugzilla report at
> > https://bugzilla.kernel.org/show_bug.cgi?id=71691
> >
> > It seems like clearing DisINTx has some effect on MSI. I don't see
On Fri, Mar 07, 2014 at 06:30:45PM -0600, Felipe Balbi wrote:
> Hi Greg,
>
> Here's my pull request for v3.15 merge window.
>
> This pull request contains patches which have been soaking in linux-next for
> quite a bit of time. I also ran everything through my 150 randconfigs script
> (which uses
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nithin Sujir
[ Upstream commit c6993dfd7db9b0c6b7ca7503a56fda9236a4710f ]
Quoting David Vrabel -
"5780 cards cannot have jumbo frames and TSO enabled together. When
jumbo frames are enabled by
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit 31efee60f489c759c341454d755a9fd13de8c03d upstream.
When a call goes out, the signing code adjusts the sequence number
upward by two to account for the request and the respons
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 8a964f44e01ad3bbc208c3e80d931ba91b9ea786 upstream.
The FH hardware will always write back to the scratch field
in commands, even host commands not just TX commands, which
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Emmanuel Grumbach
commit 25a172655f837bdb032e451f95441bb4acec51bb upstream.
This can lead to a panic if the driver isn't ready to
handle them. Since our interrupt line is shared, we can get
an
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 46f6c1aaf790be9ea3c8ddfc8f235a5f677d08e2 upstream.
snd_pcm_stop() must be called in the PCM substream lock context.
Acked-by: Mark Brown
Signed-off-by: Takashi Iwai
Signe
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 7c34158231b2eda8dcbd297be2bb1559e69cb433 upstream.
The RX replenish code doesn't handle DMA mapping failures,
which will cause issues if there actually is a failure. This
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Clements
commit c378f70adbc1bbecd9e6db145019f14b2f688c7c upstream.
Currently, when a disconnect is requested by the user (via NBD_DISCONNECT
ioctl) the return from NBD_DO_IT is undefined (
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 4fc79db178f0a0ede479b4713e00df2d106028b3 upstream.
If the device is not started, we can't read its
SRAM and attempting to do so will cause issues.
Protect the debugfs read
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 707aee401d2467baa785a697f40a6e2d9ee79ad5 upstream.
The BT_CONFIG command that is sent to the device during
startup will enable BT coex unless the module parameter
turns it
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 94543a8d4fb302817014981489f15cb3b92ec3c2 upstream.
iwl_dbgfs_fh_reg_read() can cause crashes and/or
BUG_ON in slub because the ifdefs are wrong, the
code in iwl_dump_fh() s
2014-03-07 3:34 GMT-08:00 Sebastian Hesselbarth
:
> commit 1211ce53077164e0d34641d0ca5fb4d4a7574498
> ("net: phy: resume/suspend PHYs on attach/detach")
> introduced a feature to suspend PHYs when entering halted state.
>
> Unfortunately, not all bootloaders properly power-up PHYs on reset
> and
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 60478295d6876619f8f47f6d1a5c25eaade69ee3 upstream.
snd_pcm_stop() must be called in the PCM substream lock context.
Signed-off-by: Takashi Iwai
Cc: Weng Meiling
Signed-of
501 - 600 of 751 matches
Mail list logo
