From: Jean Delvare <jdelvare@suse.de>
To: Erwan Velu <erwanaliasr1@gmail.com>
Cc: Erwan Velu <e.velu@criteo.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Mattias Jacobsson <2pi@mok.nu>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andrew Lunn <andrew@lunn.ch>,
"Darren Hart (VMware)" <dvhart@infradead.org>,
Changbin Du <changbin.du@intel.com>,
Russell King <rmk+kernel@armlinux.org.uk>,
open list <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] firmware/dmi: Report DMI Bios & EC firmware release
Date: Tue, 12 May 2020 09:37:10 +0200 [thread overview]
Message-ID: <20200512093710.74fd1dd5@endymion> (raw)
In-Reply-To: <CAL2Jzuw8K-p11kZ1DdcVtTn76GE-Y+nr-=UM86DJAiUGSNh6zg@mail.gmail.com>
Hi Erwan,
On Mon, 11 May 2020 19:10:52 +0200, Erwan Velu wrote:
> Jean, I don't see my patches in the 5.7-rc series.
> Is there anything wrong with them ?
Nothing wrong with your patch, but unfortunately I missed the merge
window and sent my pull request a few days too late, so it was not
accepted. Your patch is still in my pending queue:
http://jdelvare.nerim.net/devel/linux/jdelvare-dmi/
and therefore included in every linux-next snapshot, but it won't be
merged in v5.7, you'll have to wait for v5.8.
This is entirely my fault and I am sorry about that.
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2020-05-12 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 8:35 [PATCH] firmware/dmi: Report DMI Bios & EC firmware release Erwan Velu
2020-02-11 13:21 ` Jean Delvare
2020-02-11 13:31 ` Erwan Velu
2020-05-11 17:10 ` Erwan Velu
2020-05-12 7:37 ` 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=20200512093710.74fd1dd5@endymion \
--to=jdelvare@suse.de \
--cc=2pi@mok.nu \
--cc=andrew@lunn.ch \
--cc=andriy.shevchenko@linux.intel.com \
--cc=changbin.du@intel.com \
--cc=dvhart@infradead.org \
--cc=e.velu@criteo.com \
--cc=erwanaliasr1@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=rmk+kernel@armlinux.org.uk \
/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).