From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: gregkh@linuxfoundation.org, ming.lei@canonical.com,
corbet@lwn.net, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, dwmw2@infradead.org,
dhowells@redhat.com, seth.forshee@canonical.com,
rusty@rustcorp.com.au, mmarek@suse.cz, mjg59@srcf.ucam.org,
kyle@kernel.org, linux-security-module@vger.kernel.org,
keyrings@linux-nfs.org
Subject: Re: [PATCH 0/4] firmware_class: few small code shifts
Date: Fri, 21 Aug 2015 23:23:03 +0200 [thread overview]
Message-ID: <20150821212303.GX8051@wotan.suse.de> (raw)
In-Reply-To: <1438725604-22795-1-git-send-email-mcgrof@do-not-panic.com>
On Tue, Aug 04, 2015 at 03:00:00PM -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@suse.com>
>
> Ming, Greg,
>
> this patch set consists of a few small code shifts which would make
> it easier to add extensible firmware API code, and later firmware
> signing support. This patch set is being sent out separately as it
> does not contain any controversial changes. It should also help
> with readibility of the code.
>
> I'll be Cc'ing linux-doc, linux-security-module, and keyring folks as the
> next patch sets would start slowly diving into the topic of firmware signing
> and extending documentation, and those patches will depend on this set.
>
> There is a superfluous else branch on patch #3, its not needed because of
> the goto statement but we leave that in place to make patch #4 easier to
> read.
>
> David Howells (2):
> firmware: fold successful fw read early
> firmware: generalize reading file contents as a helper
>
> Luis R. Rodriguez (2):
> firmware: generalize "firmware" as "system data" helpers
> firmware: move completing fw into a helper
Ming, Greg,
Please let me know if there are any issues with this series.
Luis
next prev parent reply other threads:[~2015-08-21 21:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 22:00 [PATCH 0/4] firmware_class: few small code shifts Luis R. Rodriguez
2015-08-04 22:00 ` [PATCH 1/4] firmware: generalize "firmware" as "system data" helpers Luis R. Rodriguez
2015-10-04 19:16 ` Greg KH
2015-10-05 21:22 ` Luis R. Rodriguez
2015-10-06 9:08 ` Greg KH
2015-10-06 17:28 ` [PATCH 1/4] firmware: generalize "firmware" as "system data" helpers] Luis R. Rodriguez
2015-10-08 20:16 ` [PATCH 1/4] firmware: generalize "firmware" as "system data" helpers Josh Boyer
2015-12-17 19:16 ` Luis R. Rodriguez
2015-08-04 22:00 ` [PATCH 2/4] firmware: move completing fw into a helper Luis R. Rodriguez
2015-08-04 22:00 ` [PATCH 3/4] firmware: fold successful fw read early Luis R. Rodriguez
2015-08-09 13:29 ` Ming Lei
2015-08-10 16:43 ` Luis R. Rodriguez
2015-08-04 22:00 ` [PATCH 4/4] firmware: generalize reading file contents as a helper Luis R. Rodriguez
2015-08-21 21:23 ` Luis R. Rodriguez [this message]
2015-08-22 5:38 ` [PATCH 0/4] firmware_class: few small code shifts Greg KH
2015-08-22 21:18 ` Luis R. Rodriguez
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=20150821212303.GX8051@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=keyrings@linux-nfs.org \
--cc=kyle@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=ming.lei@canonical.com \
--cc=mjg59@srcf.ucam.org \
--cc=mmarek@suse.cz \
--cc=rusty@rustcorp.com.au \
--cc=seth.forshee@canonical.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).