public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL] IIO: First set of new device support etc for the 5.10 cycle
Date: Sun, 6 Sep 2020 16:11:25 +0100	[thread overview]
Message-ID: <20200906161125.725e49aa@archlinux> (raw)
In-Reply-To: <20200906145741.GA314751@kroah.com>

On Sun, 6 Sep 2020 16:57:41 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:

> On Sun, Sep 06, 2020 at 04:56:28PM +0200, Greg KH wrote:
> > On Sun, Sep 06, 2020 at 01:39:58PM +0100, Jonathan Cameron wrote:  
> > > The following changes since commit bc752d2f345bf55d71b3422a6a24890ea03168dc:
> > > 
> > >   staging: hikey9xx: Kconfig: add regulator dependency (2020-08-18 19:15:47 +0200)
> > > 
> > > are available in the Git repository at:
> > > 
> > >   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-5.10a  
> > 
> > Pulled and pushed out, thanks.  
> 
> Oops, spoke too soon, I get the following error when trying to push:
> Verifying "Fixes:"...		                
> 
> Commit: 1bebdcb928eb ("drivers/iio/humidity/hdc2010.c:305:2-3: Unneeded semicolon")
> 	Fixes tag: Fixes: 016b57638b47 ("iio: humidity: Add TI HDC20x0 support")
> 	Has these problem(s):
> 	        - Target SHA1 does not exist
> 
> Can you fix this up and send a new pull request?
Gah!  I forgot to check.  Sorry about that. New pull in a few moments.
At least it was the top patch on the tree.

Jonathan

> 
> thanks,
> 
> greg k-h


      reply	other threads:[~2020-09-06 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06 12:39 [PULL] IIO: First set of new device support etc for the 5.10 cycle Jonathan Cameron
2020-09-06 14:56 ` Greg KH
2020-09-06 14:57   ` Greg KH
2020-09-06 15: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=20200906161125.725e49aa@archlinux \
    --to=jic23@kernel.org \
    --cc=gregkh@linuxfoundation.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