public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Felipe Balbi <balbi@ti.com>, Joe Perches <joe@perches.com>,
	Andy Whitcroft <apw@canonical.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scripts: checkpatch: ignore stable commit annotation
Date: Tue, 30 Jun 2015 19:53:48 -0500	[thread overview]
Message-ID: <20150701005348.GA15251@saruman.tx.rr.com> (raw)
In-Reply-To: <20150630234554.GA13573@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]

On Tue, Jun 30, 2015 at 04:45:54PM -0700, Greg KH wrote:
> On Tue, Jun 30, 2015 at 05:42:31PM -0500, Felipe Balbi wrote:
> > On Tue, Jun 30, 2015 at 03:30:35PM -0700, Joe Perches wrote:
> > > On Tue, 2015-06-30 at 17:07 -0500, Felipe Balbi wrote:
> > > > When running scripts/checkpatch.pl on stable commits,
> > > > we always get the error for not using 12-character
> > > > commit hash abbreviation with shortlog within ("").
> > > 
> > > Looking at linux-stable v3.14.44 (randomly chosen), there
> > > are also commit entries like:
> > > 
> > >    This is commit 0f540c3a7cfb91c9d7a19eb0c95c24 upstream.
> > >  commit:  cb64edb6b89491edfdbae52ba7db9a8b8391d339 upstream
> > > 
> > > is -stable now using some script to tag these or is it
> > > freehanded and happens to be reasonably consistent?
> > 
> > afaict, Greg uses a script. Greg ?
> 
> I use a script, but my script didn't create both of those lines, only
> one of them, the bottom one.  The top one comes from David Miller's
> scripts which he uses when he sends me networking stable patches.
> 
> Never run checkpatch on stable commits, that makes no sense at all as I
> am pulling them directly from Linus's tree and there is nothing I can do
> to change anything in them, nor would I ever want to.
> 
> > > If these are really scripted, the case-insensitive /i
> > > shouldn't be necessary.
> > 
> > yeah, it was really just to be safer. What if Greg decides to change his
> > script in the future ?
> 
> You shouldn't care, as you shouldn't be running the script and thinking
> it matters, on stable tree commits.

fair enough, branch deleted. I had that hunch, but since there were some
complaining of checkpatch errors on stable commits, I thought about just
patching it up. Thanks for confirming.

cheers

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-07-01  0:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 22:07 [PATCH] scripts: checkpatch: ignore stable commit annotation Felipe Balbi
2015-06-30 22:30 ` Joe Perches
2015-06-30 22:42   ` Felipe Balbi
2015-06-30 23:45     ` Greg KH
2015-07-01  0:53       ` Felipe Balbi [this message]

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=20150701005348.GA15251@saruman.tx.rr.com \
    --to=balbi@ti.com \
    --cc=apw@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    /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