From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Greg KH <greg@kroah.com>
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>,
Patrick Havelange <patrick.havelange@essensium.com>,
William Breathitt Gray <vilhelm.gray@gmail.com>,
Lorenzo Bianconi <lorenzo@kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the staging.current tree
Date: Wed, 19 Jun 2019 08:54:16 +0100 [thread overview]
Message-ID: <20190619085416.00001d8f@huawei.com> (raw)
In-Reply-To: <20190618115131.GB21419@kroah.com>
On Tue, 18 Jun 2019 13:51:31 +0200
Greg KH <greg@kroah.com> wrote:
> On Tue, Jun 18, 2019 at 07:36:18AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > In commit
> >
> > 0c75376fa395 ("counter/ftm-quaddec: Add missing dependencies in Kconfig")
> >
> > Fixes tag
> >
> > Fixes: a3b9a99 ("counter: add FlexTimer Module Quadrature decoder counter driver")
> >
> > has these problem(s):
> >
> > - SHA1 should be at least 12 digits long
> > Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
> > or later) just making sure it is not set (or set to "auto").
> >
> > In commit
> >
> > bce0d57db388 ("iio: imu: st_lsm6dsx: fix PM support for st_lsm6dsx i2c controller")
> >
> > Fixes tag
> >
> > Fixes: c91c1c844ebd ("imu: st_lsm6dsx: add i2c embedded controller support")
> >
> > has these problem(s):
> >
> > - Subject does not match target commit subject
> > Just use
> > git log -1 --format='Fixes: %h ("%s")'
>
> Ugh.
>
> I blame Jonathan for all of these as they came in through his tree :)
>
> thanks,
>
> greg k-h
I'll keep a closer eye on this going forwards.
Thanks,
Jonathan
prev parent reply other threads:[~2019-06-19 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 21:36 linux-next: Fixes tags need some work in the staging.current tree Stephen Rothwell
2019-06-18 11:51 ` Greg KH
2019-06-19 7:54 ` Jonathan Cameron [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=20190619085416.00001d8f@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=patrick.havelange@essensium.com \
--cc=sfr@canb.auug.org.au \
--cc=vilhelm.gray@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.