From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Jithu Joseph <jithu.joseph@intel.com>
Cc: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
maurice.ma@intel.com, ravi.p.rangarajan@intel.com,
Sean V Kelley <sean.v.kelley@intel.com>,
kuo-lang.tseng@intel.com
Subject: Re: [PATCH v2 0/1] platform/x86: Add Slim Bootloader firmware update support
Date: Mon, 27 Apr 2020 13:03:38 +0300 [thread overview]
Message-ID: <CAHp75Vezc9-vTSVsTE=ce_2XRPfFVT2gHwZhwqZiRX8M=sdmmg@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VcqV3e8ecAUX+dr9h-bE+1XJ_71hJRA1b9XdouJJLD2ZA@mail.gmail.com>
On Fri, Apr 24, 2020 at 2:08 PM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Fri, Apr 24, 2020 at 1:49 AM Jithu Joseph <jithu.joseph@intel.com> wrote:
> >
> > v1 Upstream submission is available here:
> > https://lore.kernel.org/lkml/20200420194405.8281-1-jithu.joseph@intel.com
> >
>
> Pushed to my review and testing queue, thanks!
One question, though.
We use a bit different template for module names
vendor-...-wmi
(yes, with exception to TBT)
I would like to rename sbl_fwu_wmi to something like this:
intel-wmi-sbl-fw-update
What do you think?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-04-27 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 22:42 [PATCH v2 0/1] platform/x86: Add Slim Bootloader firmware update support Jithu Joseph
2020-04-23 22:42 ` [PATCH v2 1/1] platform/x86: Add Slim Bootloader firmware update signaling driver Jithu Joseph
2020-04-24 11:08 ` [PATCH v2 0/1] platform/x86: Add Slim Bootloader firmware update support Andy Shevchenko
2020-04-27 10:03 ` Andy Shevchenko [this message]
2020-04-27 19:57 ` Jithu Joseph
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='CAHp75Vezc9-vTSVsTE=ce_2XRPfFVT2gHwZhwqZiRX8M=sdmmg@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=jithu.joseph@intel.com \
--cc=kuo-lang.tseng@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maurice.ma@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=ravi.p.rangarajan@intel.com \
--cc=sean.v.kelley@intel.com \
/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).