From: Matt Fleming <matt@codeblueprint.co.uk>
To: "Stanacar, Stefan" <stefan.stanacar@intel.com>
Cc: "Baluta, Daniel" <daniel.baluta@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dvhart@infradead.org" <dvhart@infradead.org>,
"Gumbel, Matthew K" <matthew.k.gumbel@intel.com>,
"Purdila, Octavian" <octavian.purdila@intel.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"Abbas, Mohamed" <mohamed.abbas@intel.com>,
"Musca, Constantin" <constantin.musca@intel.com>
Subject: Re: [PATCH v2] efi: Introduce EFI bootloader control driver
Date: Tue, 29 Mar 2016 13:53:45 +0100 [thread overview]
Message-ID: <20160329125345.GD3625@codeblueprint.co.uk> (raw)
In-Reply-To: <1458836156.14677.9.camel@intel.com>
On Thu, 24 Mar, at 04:15:56PM, Stanacar, Stefan wrote:
>
> Ok, that's funny somehow... I wouldn't be surprised if I'd find 3 more
> variations of the same driver in different vendor trees :(.
Right. And that does add weight to getting a version merged upstream;
to discourage people carrying their own.
> I'll ping the author of the patch, thanks!
I haven't reviewed the patch in detail, but it did look like the
correct general approach.
prev parent reply other threads:[~2016-03-29 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 10:11 [PATCH v2] efi: Introduce EFI bootloader control driver Daniel Baluta
2016-03-18 11:22 ` kbuild test robot
2016-03-18 12:46 ` kbuild test robot
2016-03-18 16:15 ` Matt Fleming
2016-03-18 19:18 ` Stanacar, Stefan
2016-03-24 14:47 ` Matt Fleming
2016-03-24 16:15 ` Stanacar, Stefan
2016-03-29 12:53 ` Matt Fleming [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=20160329125345.GD3625@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=constantin.musca@intel.com \
--cc=daniel.baluta@intel.com \
--cc=dvhart@infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.k.gumbel@intel.com \
--cc=mohamed.abbas@intel.com \
--cc=octavian.purdila@intel.com \
--cc=stefan.stanacar@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