From: Jean Delvare <jdelvare@suse.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>
Subject: Re: [PATCH] firmware: dmi_scan: Fix UUID endianness for SMBIOS >= 2.6
Date: Tue, 1 Mar 2016 12:15:39 +0100 [thread overview]
Message-ID: <20160301121539.508a8b29@endymion> (raw)
In-Reply-To: <20160301061124.GD3200@kroah.com>
Hi Greg,
On Tue, 01 Mar 2016 06:11:25 +0000, Greg KH wrote:
> On Mon, Jan 11, 2016 at 10:20:49AM +0100, Jean Delvare wrote:
> > Hi all,
> >
> > This commit:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ff4319dc7cd58c92b389960e375038335d157a60
> >
> > was supposed to be tagged with:
> >
> > Cc: stable@vger.kernel.org [v3.10+]
> >
> > But unfortunately I forgot to refresh the patch header before
> > committing. So please treat this commit as if this tag was present.
> > Sorry for the extra work.
>
> It doesn't apply to 3.14-stable or 3.10-stable, so if you want it there,
> can you please provide a backport?
I double-checked the code and I don't think these branches are affected
by the bug, so no backporting is needed. I have no idea what made me
think otherwise back then, sorry for the noise.
The bug was introduced by commit 95be58df74 ("firmware: dmi_scan: Use
full dmi version for SMBIOS3") which made it into kernel v4.1. I'm
afraid the two commits I mentioned in the log message are just plain
wrong :( Only kernel branches v4.1 to v4.3 need this fix.
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2016-03-01 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 9:20 [PATCH] firmware: dmi_scan: Fix UUID endianness for SMBIOS >= 2.6 Jean Delvare
2016-03-01 6:11 ` Greg KH
2016-03-01 11:15 ` Jean Delvare [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=20160301121539.508a8b29@endymion \
--to=jdelvare@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.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