From: Greg KH <gregkh@linuxfoundation.org>
To: "Paraschiv, Andra-Irina" <andraprs@amazon.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Anthony Liguori <aliguori@amazon.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Colm MacCarthaigh <colmmacc@amazon.com>,
David Duncan <davdunc@amazon.com>,
Bjoern Doebel <doebel@amazon.de>,
David Woodhouse <dwmw@amazon.co.uk>,
Frank van der Linden <fllinden@amazon.com>,
Alexander Graf <graf@amazon.de>, Karen Noel <knoel@redhat.com>,
Martin Pohlack <mpohlack@amazon.de>, Matt Wilson <msw@amazon.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Balbir Singh <sblbir@amazon.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Stewart Smith <trawets@amazon.com>,
Uwe Dannowski <uwed@amazon.de>,
Vitaly Kuznetsov <vkuznets@redhat.com>, kvm <kvm@vger.kernel.org>,
ne-devel-upstream <ne-devel-upstream@amazon.com>
Subject: Re: [PATCH v9 14/18] nitro_enclaves: Add Kconfig for the Nitro Enclaves driver
Date: Tue, 22 Sep 2020 18:20:49 +0200 [thread overview]
Message-ID: <20200922162049.GA2299429@kroah.com> (raw)
In-Reply-To: <358e7470-b841-52fe-0532-e1154ef0e93b@amazon.com>
On Tue, Sep 22, 2020 at 05:13:02PM +0300, Paraschiv, Andra-Irina wrote:
>
>
> On 21/09/2020 15:34, Paraschiv, Andra-Irina wrote:
> >
> >
> > On 14/09/2020 20:23, Paraschiv, Andra-Irina wrote:
> > >
> > >
> > > On 14/09/2020 18:59, Greg KH wrote:
> > > > On Fri, Sep 11, 2020 at 05:11:37PM +0300, Andra Paraschiv wrote:
> > > > > Signed-off-by: Andra Paraschiv <andraprs@amazon.com>
> > > > > Reviewed-by: Alexander Graf <graf@amazon.com>
> > > > I can't take patches without any changelog text at all, sorry.
> > > >
> > > > Same for a few other patches in this series :(
> > > >
> > >
> > > I can move the changelog text before the Sob tag(s) for all the
> > > patches. I also can add a summary phrase in the commit message for
> > > the commits like this one that have only the commit title and Sob &
> > > Rb tags.
> > >
> > > Would these updates to the commit messages match the expectations?
> > >
> > > Let me know if remaining feedback to discuss and I should include as
> > > updates in v10. Otherwise, I can send the new revision with the
> > > updated commit messages.
> > >
> > > Thanks for review.
> >
> > Here we go, I published v10, including the updated commit messages and
> > rebased on top of v5.9-rc6.
> >
> > https://lore.kernel.org/lkml/20200921121732.44291-1-andraprs@amazon.com/
> >
> > Any additional feedback, open to discuss.
> >
> > If all looks good, we can move forward as we've talked before, to have
> > the patch series on the char-misc branch and target v5.10-rc1.
>
> Thanks for merging the patch series on the char-misc-testing branch and for
> the review sessions we've had.
>
> Let's see how all goes next; if anything in the meantime to be done (e.g.
> and not coming via auto-generated mails), just let me know.
Will do, thanks for sticking with this and cleaning it up to look a lot
better than the original submission.
Now comes the real work, maintaining it for the next 10 years :)
greg k-h
next prev parent reply other threads:[~2020-09-22 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200911141141.33296-1-andraprs@amazon.com>
[not found] ` <20200911141141.33296-15-andraprs@amazon.com>
2020-09-14 15:59 ` [PATCH v9 14/18] nitro_enclaves: Add Kconfig for the Nitro Enclaves driver Greg KH
2020-09-14 17:23 ` Paraschiv, Andra-Irina
2020-09-21 12:34 ` Paraschiv, Andra-Irina
2020-09-22 14:13 ` Paraschiv, Andra-Irina
2020-09-22 16:20 ` Greg KH [this message]
2020-09-22 17:06 ` Paraschiv, Andra-Irina
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=20200922162049.GA2299429@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aliguori@amazon.com \
--cc=andraprs@amazon.com \
--cc=benh@kernel.crashing.org \
--cc=colmmacc@amazon.com \
--cc=davdunc@amazon.com \
--cc=doebel@amazon.de \
--cc=dwmw@amazon.co.uk \
--cc=fllinden@amazon.com \
--cc=graf@amazon.de \
--cc=knoel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpohlack@amazon.de \
--cc=msw@amazon.com \
--cc=ne-devel-upstream@amazon.com \
--cc=pbonzini@redhat.com \
--cc=sblbir@amazon.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=trawets@amazon.com \
--cc=uwed@amazon.de \
--cc=vkuznets@redhat.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