linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Artur Rojek <contact@artur-rojek.eu>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Maarten ter Huurne <maarten@treewalker.org>
Subject: Re: linux-next: Fixes tag needs some work in the staging.current tree
Date: Mon, 29 Jul 2019 09:24:53 +0100	[thread overview]
Message-ID: <20190729092453.00005d8b@huawei.com> (raw)
In-Reply-To: <20190728131355.GA5007@kroah.com>

On Sun, 28 Jul 2019 15:13:55 +0200
Greg KH <greg@kroah.com> wrote:

> On Sun, Jul 28, 2019 at 11:01:47PM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > In commit
> > 
> >   5a304e1a4ea0 ("IIO: Ingenic JZ47xx: Set clock divider on probe")
> > 
> > Fixes tag
> > 
> >   Fixes: 1a78daea107d ("iio: adc: probe should set clock divider")
> > 
> > has these problem(s):
> > 
> >   - Subject does not match target commit subject
> >     Just use
> > 	git log -1 --format='Fixes: %h ("%s")'
> > 
> > Did you mean
> > 
> > Fixes: 1a78daea107d ("IIO: add Ingenic JZ47xx ADC driver.")  
> 
> Jonathan, I'm guessing this was your fault...
> 
> greg k-h

Indeed should have spotted that one.
Sorry about that, I'll check these more thoroughly.

Thanks for pointing it out Stephen!

Jonathan


  reply	other threads:[~2019-07-29  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28 13:01 linux-next: Fixes tag needs some work in the staging.current tree Stephen Rothwell
2019-07-28 13:13 ` Greg KH
2019-07-29  8:24   ` Jonathan Cameron [this message]
2019-10-10 20:42 Stephen Rothwell
2019-10-11  8:10 ` Jonathan Cameron
2019-10-11  8:29   ` Greg KH
2019-10-11 10:36     ` 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=20190729092453.00005d8b@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=contact@artur-rojek.eu \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=maarten@treewalker.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;
as well as URLs for NNTP newsgroup(s).