From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: "Stanacar,
Stefan" <stefan.stanacar-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "Baluta,
Daniel" <daniel.baluta-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"dvhart-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org"
<dvhart-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
"Gumbel,
Matthew K"
<matthew.k.gumbel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Purdila,
Octavian"
<octavian.purdila-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Abbas,
Mohamed" <mohamed.abbas-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Musca,
Constantin"
<constantin.musca-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
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.
WARNING: multiple messages have this Message-ID (diff)
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.
next prev parent reply other threads:[~2016-03-29 12:53 UTC|newest]
Thread overview: 15+ 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 10:11 ` Daniel Baluta
[not found] ` <1458295910-26557-1-git-send-email-daniel.baluta-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-03-18 11:22 ` kbuild test robot
2016-03-18 11:22 ` kbuild test robot
2016-03-18 12:46 ` kbuild test robot
2016-03-18 12:46 ` kbuild test robot
2016-03-18 16:15 ` Matt Fleming
2016-03-18 16:15 ` Matt Fleming
[not found] ` <20160318161505.GU2619-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-03-18 19:18 ` Stanacar, Stefan
2016-03-18 19:18 ` Stanacar, Stefan
2016-03-24 14:47 ` Matt Fleming
[not found] ` <20160324144741.GA4328-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-03-24 16:15 ` Stanacar, Stefan
2016-03-24 16:15 ` Stanacar, Stefan
[not found] ` <1458836156.14677.9.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-03-29 12:53 ` Matt Fleming [this message]
2016-03-29 12:53 ` Matt Fleming
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-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=constantin.musca-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=daniel.baluta-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dvhart-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matthew.k.gumbel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mohamed.abbas-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=octavian.purdila-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=stefan.stanacar-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.