From: Greg KH <gregkh@linuxfoundation.org>
To: "Jörg-Volker Peetz" <jvpeetz@web.de>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 4.3.1
Date: Thu, 10 Dec 2015 12:20:10 -0500 [thread overview]
Message-ID: <20151210172010.GA23660@kroah.com> (raw)
In-Reply-To: <5669B271.6070006@web.de>
On Thu, Dec 10, 2015 at 06:12:17PM +0100, J�rg-Volker Peetz wrote:
> Greg KH wrote on 12/09/15 21:16:
> > I'm announcing the release of the 4.3.1 kernel.
> >
> > All users of the 4.3 kernel series must upgrade.
> >
> > The updated 4.3.y git tree can be found at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.3.y
> > and can be browsed at the normal kernel.org git web browser:
> > http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> >
> > thanks,
> >
> > greg k-h
> >
> <snip>
>
> Trying this stable patch on an older HP Pavilion dv7 laptop fails while version
> 4.3.0 works.
> It seems that no kernel modules get loaded, resulting in network and several
> input devices missing. Only difference I see in dmesg is
>
> Problem loading in-kernel X.509 certificate (-74)
>
> Attaching my config which is the same as for 4.3.0.
> Any idea?
Yes, commit cc25b994acfbc901429da682d0f73c190e960206 in Linus's tree
should fix this, but this should also be an issue for you with 4.3.0, I
don't think anything specifically broke this between .0 and .1.
I'll try to get a 4.3.2 out later today with this fix.
thanks,
greg k-h
prev parent reply other threads:[~2015-12-10 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 20:16 Linux 4.3.1 Greg KH
2015-12-09 20:16 ` Greg KH
2015-12-10 17:12 ` Jörg-Volker Peetz
2015-12-10 17:20 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151210172010.GA23660@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=jvpeetz@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).