On pią, 2015-02-06 at 18:42 -0800, Darren Hart wrote:
> On Tue, Jan 27, 2015 at 12:30:19PM +0100, Krzysztof Kozlowski wrote:
> > The return value of power_supply_register() call was not checked and
> > even on error probe() function returned 0. If registering failed then
> > during unbind the drive
On Thu, 2015-02-05 at 10:22 +, Luis Henriques wrote:
> On Wed, Feb 04, 2015 at 07:42:30PM +, Ben Hutchings wrote:
> > On Tue, 2015-02-03 at 11:33 +, Luis Henriques wrote:
> > > On Thu, Jan 29, 2015 at 01:07:40AM +, Ben Hutchings wrote:
> > > > On Thu, 2015-01-29 at 11:27 +1100, Mich
Hi, Greg,
The commit 88b5d12 ("mm: propagate error from stack expansion even for
guard page") for 3.10-stable makes the testcase get "bus error", while
it had "segmentation fault" in older kernels.
= testcase =
int main(void)
{
main();
return 0;
}
Thes
From: Linus Torvalds
commit 9c145c56d0c8a0b62e48c8d71e055ad0fb2012ba upstream
The stack guard page error case has long incorrectly caused a SIGBUS
rather than a SIGSEGV, but nobody actually noticed until commit
fee7e49d4514 ("mm: propagate error from stack expansion even for guard
page") because
From: Linus Torvalds
commit 33692f27597fcab536d7cbbcc8f52905133e4aa7 upstream
The core VM already knows about VM_FAULT_SIGBUS, but cannot return a
"you should SIGSEGV" error, because the SIGSEGV case was generally
handled by the caller - usually the architecture fault handler.
That results in l
On 01/16/2015 08:05 PM, Daniel Vetter wrote:
> On Thu, Jan 15, 2015 at 08:44:00PM +, Chris Wilson wrote:
>> On Thu, Jan 15, 2015 at 08:36:15PM +0100, Daniel Vetter wrote:
>>> On Wed, Jan 14, 2015 at 9:34 PM, Chris Wilson
>>> wrote:
This (partially) reverts
commit 5537252b6b6d
Hi Vicky,
unfortunately your patch format is broken.
> @@ -148,7 +148,7 @@ static int tpm_ibmvtpm_send(struct tpm_chip *chip,
> u8 *buf, size_t count)
Seems like it got line-wrapped or something. I couldn't repair without
applying each line manually.
Please resend (and include a description)
On Saturday, February 07, 2015 09:53:53 AM Hans de Goede wrote:
> Backlight control through the native intel interface does not work properly
> on the Samsung 510R, where as using the acpi_video interface does work, add
> a quirk for this.
>
> BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1
alpha:allmodconfig
arm:at91_dt_defconfig
i386:allyesconfig
i386:allmodconfig
mips:allmodconfig
powerpc:allmodconfig
spacrc64:allmodconfig
x86_64:allyesconfig
x86_64:allmodconfig
xtensa:allmodconfig
sound/soc/codecs/wm8731.c: In function 'wm8731_i2c_probe':
sound/soc/codecs/wm8731.c:737:2: error:
On 02/06/2015, 06:59 PM, Mark Rutland wrote:
> commit 44b82b7700d05a52cd983799d3ecde1a976b3bed upstream.
>
> [backport to 3.12.x: fold in missing MIDR_EL1 recording]
Now applied. Thanks.
--
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a messa
10 matches
Mail list logo