Hello, On Thu, Jul 20, 2023 at 11:46:31AM +0200, Uwe Kleine-König wrote: > On Thu, Jul 20, 2023 at 11:27:51AM +0200, Hans Verkuil wrote: > > On 20/07/2023 11:02, Uwe Kleine-König wrote: > > > Is this patch still (or at all) on someone's radar for merging? > > > > I merged this yesterday in our staging tree for 6.6. Did you get an email > > from patchwork? > > > > https://patchwork.linuxtv.org/project/linux-media/patch/20230626090533.556406-1-u.kleine-koenig@xxxxxxxxxxxxxx/ > > > > I also merged yesterday your patch converting three more drivers: > > > > https://patchwork.linuxtv.org/project/linux-media/patch/20230718204541.3955386-1-u.kleine-koenig@xxxxxxxxxxxxxx/ > > Indeed I got a mail about that, but missed that here. (Too many patches > in float here, so I usually check the submission thread and next before > asking about the status. For me it would be a useful improvement if the > mail would be sent in reply to the respecitve mailing list thread.) Today I stumbled again over this patch because it didn't appear in next as of today. Is this intended? Rechecking said mail, it only mentions "git:media_stage/master" in the Subject and the body only has " This is an automatic generated email to let you know that the following patch were queued:" plus the patch. Additionally to what I wrote before it would also be great if the the git repo's public URL were mentioned, ideally together with the branch name as git request-pull generates it for easy cut'n'paste after "git fetch". Thanks for considering, Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | https://www.pengutronix.de/ |
Attachment:
signature.asc
Description: PGP signature
