Re: [PATCH v2] Documentation: bno055: separate SPDX identifier and page title

[Jonathan Cameron]

On Tue, 5 Jul 2022 11:02:32 +0200
Andy Shevchenko <andy.shevchenko@xxxxxxxxx> wrote:

> On Tue, Jul 5, 2022 at 3:13 AM Bagas Sanjaya <bagasdotme@xxxxxxxxx> wrote:
> > On 7/5/22 02:49, Andy Shevchenko wrote:  
> 
> ...
> 
> > >> Cc: Jonathan Corbet <corbet@xxxxxxx>
> > >> Cc: Andrea Merello <andrea.merello@xxxxxx>
> > >> Cc: Jonathan Cameron <jic23@xxxxxxxxxx>
> > >> Cc: Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx>
> > >> Cc: Lars-Peter Clausen <lars@xxxxxxxxxx>
> > >> Cc: Rob Herring <robh+dt@xxxxxxxxxx>
> > >> Cc: Matt Ranostay <matt.ranostay@xxxxxxxxxxxx>
> > >> Cc: Alexandru Ardelean <ardeleanalex@xxxxxxxxx>
> > >> Cc: jacopo@xxxxxxxxxx
> > >> Cc: linux-iio@xxxxxxxxxxxxxxx
> > >> Cc: devicetree@xxxxxxxxxxxxxxx
> > >> Cc: linux-kernel@xxxxxxxxxxxxxxx (open list)  
> > >
> > > It's a very noisy Cc list which will go in the git history. Instead,
> > > use --to and --cc parameters of `git format-patch`. Maintainers
> > > usually use `b4` tool that adds a Link tag to the patch itself on the
> > > Lore archive which will keep track on the Cc list anyway.  
> 
> > Thanks for reminding me.
> >
> > I think something like `b4 am -l`, right?
> >
> > Anyway, should I resend (reroll)?  
> 
> Depends on the maintainer's wishes. Maybe they can drop them when
> applying, I dunno.
> 

At the moment this is a fix to a series we haven't actually accepted.
Nice to have an all, but up to Andrea on how to handle it.
One reasonable option would be just to squish it into the original
patch for v7 with an appropriate note in the patch description / changelog.

Thanks,

Jonathan