Re: [PATCH v2 0/4] ASoC: rt5677: Refactor GPIO and use device_get_match_data()

[Konstantin Ryabitsev <konstantin@linuxfoundation.org>]

On Wed, Jul 12, 2023 at 07:59:24PM +0100, Mark Brown wrote:
> > But I think the complaint was about the merge commits being cut off:
> > 
> >     https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=5a043fd5c74c66897ad113e5ee34e9361e3f4c11
> 
> Oh, I see.  The commit in the mail looked like it might be off and it
> was in reply to the applied mail so I thought that was what was being
> referenced.
> 
> > When I try "b4 shazam -M", the merge commit looks different to me, so I want
> > to understand how the merge commit is generated in your workflow.
> 
> That's generated by my scripts based on the .cover that b4 writes out
> and some sed at the point where a merge is done.  There's a bunch of CI
> happens between applying the patches and me actually merging them so I
> don't use b4 for that bit.  It's just picking the subject line out with
> sed so there's no way it's going to handle multi-line subjects.

Will it help if b4 optionally writes out a foo.merge file in addition to
foo.cover in the same format as with "b4 shazam"?

-K