[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YSkDounI6wcZP/Dt@kroah.com>
Date: Fri, 27 Aug 2021 17:24:18 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: "Paraschiv, Andra-Irina" <andraprs@...zon.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Alexandru Ciobotaru <alcioa@...zon.com>,
Kamal Mostafa <kamal@...onical.com>,
Alexandru Vasile <lexnv@...zon.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Stefano Garzarella <sgarzare@...hat.com>,
Stefan Hajnoczi <stefanha@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
kvm <kvm@...r.kernel.org>,
ne-devel-upstream <ne-devel-upstream@...zon.com>
Subject: Re: [PATCH v2 1/7] nitro_enclaves: Enable Arm64 support
On Fri, Aug 27, 2021 at 06:02:57PM +0300, Paraschiv, Andra-Irina wrote:
>
>
> On 27/08/2021 17:25, Greg KH wrote:
> > On Fri, Aug 27, 2021 at 04:32:24PM +0300, Andra Paraschiv wrote:
> > > Update the kernel config to enable the Nitro Enclaves kernel driver for
> > > Arm64 support.
> > >
> > > Changelog
> > >
> > > v1 -> v2
> > >
> > > * No changes.
> > >
> > changelogs for different all go below the --- line, as is documented.
> > No need for them here in the changelog text itself, right?
> >
> > Please fix up and send a v3 series.
>
> Alright, I can modify the patches so that the changelog is after the line.
>
> I followed the same pattern as the initial time, when I received feedback to
> have the changelogs in the commit message, before SoB(s).
Only the crazy drm developers seem to use that format :)
> But that's fine with me, I can switch to this way of doing it, as mentioned
> also in the docs.
Thank you.
greg k-h
Powered by blists - more mailing lists