public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: linux-next: Signed-off-by missing for commits in the v4l-dvb tree
Date: Tue, 1 Sep 2020 14:10:33 +0200	[thread overview]
Message-ID: <20200901141033.74489cff@coco.lan> (raw)
In-Reply-To: <20200901125216.5ae2ecbf@coco.lan>

Em Tue, 1 Sep 2020 12:52:16 +0200
Mauro Carvalho Chehab <mchehab@kernel.org> escreveu:

> Hi Julia,
> 
> Em Tue, 1 Sep 2020 12:05:51 +0200 (CEST)
> Julia Lawall <julia.lawall@inria.fr> escreveu:
> 
> > On Tue, 1 Sep 2020, Stephen Rothwell wrote:
> > 
> > > Hi all,
> > >
> > > Commits
> > >
> > >   063a27cb9820 ("media: tm6000: drop unnecessary list_empty")
> > >   1c047c859965 ("media: saa7134: drop unnecessary list_empty")
> > >   3fdcea7c763a ("media: cx231xx: drop unnecessary list_empty")
> > >
> > > are missing a Signed-off-by from their author.  
> > 
> > My record of these patches all have their Signed-off-bys.  Mauro, do you
> > want me to send them again?
> 
> No need. Yeah, I received them with your SoB, at least on my e-mail.
> 
> The one I applied came from this pull request:
> 
> 	https://patchwork.linuxtv.org/project/linux-media/patch/87327e52-44cc-a2b8-c3fe-619bd6022264@xs4all.nl/
> 
> Unfortunately, it sounds that Hans already dropped the original tag:
> 
> 	https://git.linuxtv.org/hverkuil/media_tree.git/refs/tags
> 
> So, hard to know where the SoB got dropped. It could be due to some
> bug on my scripts - or it can be due to some issue when Hans picked
> them.
> 
> In any case, I'll rewrite the git history with your SoB properly
> added.


Ok, I was able to find a backup of the patch I applied, as my scripts
safe a copy before applying.

One of the scripts I use has a logic to get just the header of a message,
excluding the diff:

	$ githead.pl 0019-0040-cx231xx-drop-unnecessary-list_empty.patch
	[media] cx231xx: drop unnecessary list_empty
	# Original subject: [PATCH 3/7] [media] cx231xx: drop unnecessary list_empty
	
	# Meta data:
	GIT_AUTHOR_DATE=1595761108
	GIT_AUTHOR_NAME=Julia Lawall
	GIT_AUTHOR_EMAIL=Julia.Lawall@inria.fr
	# X-Patchwork-Submitter: Julia Lawall <Julia.Lawall@inria.fr>
	# X-Patchwork-Id: 65835
	# X-IronPort-AV: E=Sophos;i="5.75,398,1589234400";    d="scan'208";a="355309545"
	# Cc: kernel-janitors@vger.kernel.org, linux-media@vger.kernel.org, linux-kernel@vger.kernel.org # Date: Sun, 26 Jul 2020 12:58:28 +0200
	# X-LSpam-Score: -2.4 (--)
	# X-LSpam-Report: No,  score=-2.4 required=5.0  tests=BAYES_00=-1.9,HEADER_FROM_DIFFERENT_DOMAINS=0.5,MAILING_LIST_MULTI=-1  autolearn=ham autolearn_force=no
	#
	list_for_each_entry is able to handle an empty list.
	The only effect of avoiding the loop is not initializing the
	index variable.
	Drop list_empty tests in cases where these variables are not
	used.
	
	Note that list_for_each_entry is defined in terms of list_first_entry,
	which indicates that it should not be used on an empty list.  But in
	list_for_each_entry, the element obtained by list_first_entry is not
	really accessed, only the address of its list_head field is compared
	to the address of the list head, so the list_first_entry is safe.
	
	The semantic patch that makes this change is as follows:
	(http://coccinelle.lip6.fr/)
	
	<smpl>
	@@
	expression x,e;
	iterator name list_for_each_entry;
	statement S;
	identifier i;
	@@
	
	-if (!(list_empty(x))) {
	   list_for_each_entry(i,x,...) S

Among other things, such script ignores everything after /^---\n/
regex.

Yet, the smpl patch hit some bug on it, making it lose this part:

	- }
	 ... when != i
	? i = e
	</smpl>
	
	Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
	Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>

Because it contains this regex: /^-\s/

Making it think that this would have some mangled patch on it.

That part came from the old days where we used CVS (and later
mercurial) and some diffs were not strictly following the
pattern generated by git those days.

I changed my script to avoid this issue to happen again.

Thanks,
Mauro

  reply	other threads:[~2020-09-01 12:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01  9:03 linux-next: Signed-off-by missing for commits in the v4l-dvb tree Stephen Rothwell
2020-09-01 10:05 ` Julia Lawall
2020-09-01 10:52   ` Mauro Carvalho Chehab
2020-09-01 12:10     ` Mauro Carvalho Chehab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-30 10:59 Stephen Rothwell
2019-05-23 14:05 Stephen Rothwell
2019-05-23 14:10 ` Sakari Ailus
2019-05-23 14:20   ` Mauro Carvalho Chehab
2018-05-16 21:37 Stephen Rothwell
2018-05-17  7:17 ` Sakari Ailus
2018-05-17 10:05   ` Mauro Carvalho Chehab
2017-10-31 11:42 Stephen Rothwell
2017-09-25 23:09 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200901141033.74489cff@coco.lan \
    --to=mchehab@kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=julia.lawall@inria.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox