From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <groeck@google.com>
Cc: Ross Zwisler <zwisler@google.com>,
Duncan Laurie <dlaurie@chromium.org>,
furquan@chromium.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] gsmi: Google specific firmware patches
Date: Mon, 15 Oct 2018 20:30:57 +0200 [thread overview]
Message-ID: <20181015183057.GA11514@kroah.com> (raw)
In-Reply-To: <CABXOdTfUKWejqTxvtcH_O6SKaWDRGcu5qCVafTstm-r8y7ke1Q@mail.gmail.com>
On Sat, Oct 13, 2018 at 03:44:45PM -0700, Guenter Roeck wrote:
> On Fri, Oct 12, 2018 at 9:04 AM Ross Zwisler <zwisler@google.com> wrote:
>
> > This series contains some Google specific firmware patches that we've
> > been carrying out of tree. I've updated the changelog for each so that
> > it is suitable for upstream, and I've retested them to make sure I know
> > what the patches are doing.
> >
> > Duncan Laurie (3):
> > gsmi: Fix bug in append_to_eventlog sysfs handler
> > gsmi: Add coreboot to list of matching BIOS vendors
> > gsmi: Remove autoselected dependency on EFI and EFI_VARS
> >
> > Furquan Shaikh (1):
> > gsmi: Add GSMI commands to log S0ix info
> >
> >
> For the series: Reviewed-by: Guenter Roeck <groeck@chromium.org>
>
> Greg, please let me know if I should send this for every patch.
Nope, this works.
greg k-h
prev parent reply other threads:[~2018-10-15 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 16:04 [PATCH 0/4] gsmi: Google specific firmware patches Ross Zwisler
2018-10-12 16:04 ` [PATCH 1/4] gsmi: Fix bug in append_to_eventlog sysfs handler Ross Zwisler
2018-10-12 16:04 ` [PATCH 2/4] gsmi: Add coreboot to list of matching BIOS vendors Ross Zwisler
2018-10-12 16:04 ` [PATCH 3/4] gsmi: Remove autoselected dependency on EFI and EFI_VARS Ross Zwisler
2018-10-12 16:04 ` [PATCH 4/4] gsmi: Add GSMI commands to log S0ix info Ross Zwisler
[not found] ` <CABXOdTfUKWejqTxvtcH_O6SKaWDRGcu5qCVafTstm-r8y7ke1Q@mail.gmail.com>
2018-10-15 18:30 ` Greg Kroah-Hartman [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=20181015183057.GA11514@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dlaurie@chromium.org \
--cc=furquan@chromium.org \
--cc=groeck@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwisler@google.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