[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YZvQH3llm6GtihPi@smile.fi.intel.com>
Date: Mon, 22 Nov 2021 19:15:11 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Mark Brown <broonie@...nel.org>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 2/2] spi: Fix multi-line comment style
On Mon, Nov 22, 2021 at 07:09:50PM +0200, Andy Shevchenko wrote:
> On Mon, Nov 22, 2021 at 03:47:53PM +0000, Mark Brown wrote:
> > On Fri, Nov 19, 2021 at 07:37:18PM +0200, Andy Shevchenko wrote:
> > > /*
> > > * Fix multi-line comment style as in this short example. Pay attention
> > > * to the capitalization, period and starting line of the text.
> > > */
> > >
> > > While at it, split the (supposedly short) description of couple of functions
> > > to summary (short description) and (long) description.
> >
> > This doesn't apply against current code, please check and resend.
>
> I have merged your for-next branch (is it correct approach) on top of v5.16-rc2
> and patches are applied cleanly. Is it something addition I should care about?
cherry-pick also works, however this series doesn't applied cleanly (I used
`b4`). It means that I sent version before the final one. Sorry for that,
I will resend soon.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists