[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250313113030.GA24356@mazurka.cambridge.arm.com>
Date: Thu, 13 Mar 2025 11:30:30 +0000
From: Mikołaj Lenczewski <miko.lenczewski@....com>
To: Suzuki K Poulose <suzuki.poulose@....com>
Cc: ryan.roberts@....com, yang@...amperecomputing.com, corbet@....net,
catalin.marinas@....com, will@...nel.org, jean-philippe@...aro.org,
robin.murphy@....com, joro@...tes.org, akpm@...ux-foundation.org,
mark.rutland@....com, joey.gouly@....com, maz@...nel.org,
james.morse@....com, broonie@...nel.org, anshuman.khandual@....com,
oliver.upton@...ux.dev, ioworker0@...il.com, baohua@...nel.org,
david@...hat.com, jgg@...pe.ca,
shameerali.kolothum.thodi@...wei.com, nicolinc@...dia.com,
mshavit@...gle.com, jsnitsel@...hat.com, smostafa@...gle.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, iommu@...ts.linux.dev
Subject: Re: [PATCH v3 0/3] Initial BBML2 support for contpte_convert()
On Thu, Mar 13, 2025 at 11:22:07AM +0000, Suzuki K Poulose wrote:
> Hi Miko,
>
> On 13/03/2025 10:41, Mikołaj Lenczewski wrote:
> > Hi All,
> >
> Nothing about the patch functionality, but :
>
> Minor nit: Generally it is a good idea to add "What changed" from the
> previous posting. That gives the reviewers an idea of what to look for
> in the new version. Something like:
>
> Changes since V2:
> {Adding a link to the posting is an added bonus, as we can look up the
> discussions easily}
> - blah blah
> - ..
>
>
> Cheers
> Suzuki
Ah, yes. My apologies. Will make sure to include such a changelog with
links to previous versions in future. I do not know why I did not
include it here, other than it not crossing my mind...
--
Kind regards,
Mikołaj Lenczewski
Powered by blists - more mailing lists