All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL] 2nd set of IIO features and cleanup etc for 5.13
Date: Wed, 7 Apr 2021 08:35:41 +0200	[thread overview]
Message-ID: <YG1SvdUpcSSc2ZsK@kroah.com> (raw)
In-Reply-To: <20210406220555.0d6bc9b6@jic23-huawei>

On Tue, Apr 06, 2021 at 10:05:55PM +0100, Jonathan Cameron wrote:
> The following changes since commit 9c15db92a8e56bcde0f58064ac1adc28c0579b51:
> 
>   Merge tag 'iio-for-5.13a' of https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next (2021-03-26 12:09:47 +0100)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-5.13b

It looks like I had a minor cleanup fix to one of the files you removed
from staging in my tree, but that was reasy to resolve.

However, I got the following error when trying to push these out:

Commit: b3c20190dd32 ("iio: Fix iio_read_channel_processed_scale()")
	Fixes tag: Fixes: dc98269f7c7d ("iio: Provide iio_read_channel_processed_scale() API")
	Has these problem(s):
	        - Target SHA1 does not exist

Where did that git commit id come from?

Can you fix that up please?

thanks,

greg k-h

  reply	other threads:[~2021-04-07  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 21:05 [PULL] 2nd set of IIO features and cleanup etc for 5.13 Jonathan Cameron
2021-04-07  6:35 ` Greg KH [this message]
2021-04-07  7:43   ` Jonathan Cameron
2021-04-07  7:59     ` Jonathan Cameron
2021-04-07  8:09       ` Greg KH

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=YG1SvdUpcSSc2ZsK@kroah.com \
    --to=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 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.