[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160329125345.GD3625@codeblueprint.co.uk>
Date: Tue, 29 Mar 2016 13:53:45 +0100
From: Matt Fleming <matt@...eblueprint.co.uk>
To: "Stanacar, Stefan" <stefan.stanacar@...el.com>
Cc: "Baluta, Daniel" <daniel.baluta@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dvhart@...radead.org" <dvhart@...radead.org>,
"Gumbel, Matthew K" <matthew.k.gumbel@...el.com>,
"Purdila, Octavian" <octavian.purdila@...el.com>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
"Abbas, Mohamed" <mohamed.abbas@...el.com>,
"Musca, Constantin" <constantin.musca@...el.com>
Subject: Re: [PATCH v2] efi: Introduce EFI bootloader control driver
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.
Powered by blists - more mailing lists