public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>
Subject: Re: [PULL] Second set of IIO fixes for the 5.5 cycle.
Date: Tue, 14 Jan 2020 10:11:40 +0000	[thread overview]
Message-ID: <20200114101140.00003576@Huawei.com> (raw)
In-Reply-To: <20200113110639.GA5809@kroah.com>

On Mon, 13 Jan 2020 12:06:39 +0100
Greg KH <gregkh@linuxfoundation.org> wrote:

> On Sun, Jan 05, 2020 at 11:00:51AM +0000, Jonathan Cameron wrote:
> > The following changes since commit c05c403b1d123031f86e65e867be2c2e9ee1e7e3:
> > 
> >   staging: wfx: fix wrong error message (2019-12-18 15:51:06 +0100)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-5.5b  
> 
> I get this check warning when trying to push these:
> 
> Commit: 80d92ea5f865 ("iio: light: vcnl4000: Fix scale for vcnl4040")
> 	Fixes tag: Fixes: 5a441aade5b3 ("light: vcnl4000 add support for the VCNL4040 proximity and light sensor")
> 	Has these problem(s):
> 	        - Subject does not match target commit subject
> 	          Just use
> 		                git log -1 --format='Fixes: %h ("%s")'
> 
> I'll fix this up by hand, but note that this changes the git sha1, so if
> you pull you will see a merge.
> 
> thanks,
> 
> greg k-h

Gah! Sorry about that. I really need to find the time to get scripting setup around
this as trying to remember to check by hand is clearly not working.

Thanks for fixing it up.

Jonathan


      reply	other threads:[~2020-01-14 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05 11:00 [PULL] Second set of IIO fixes for the 5.5 cycle Jonathan Cameron
2020-01-12 11:46 ` Jonathan Cameron
2020-01-12 11:52   ` Greg KH
2020-01-12 16:35     ` Jonathan Cameron
2020-01-13 11:06 ` Greg KH
2020-01-14 10:11   ` 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=20200114101140.00003576@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@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