All of lore.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>,
	"William Breathitt Gray" <vilhelm.gray@gmail.com>
Subject: Re: [PULL] 1st set of counter subsystem new features for the 5.16 cycle.
Date: Mon, 18 Oct 2021 16:48:46 +0100	[thread overview]
Message-ID: <20211018164846.0000470b@Huawei.com> (raw)
In-Reply-To: <YW2WjGuci2d+gK5L@kroah.com>

On Mon, 18 Oct 2021 17:45:16 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:

> On Sun, Oct 17, 2021 at 11:27:17AM +0100, Jonathan Cameron wrote:
> > The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:
> > 
> >   Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)
> > 
> > are available in the Git repository at:
> > 
> >   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/counter-for-5.16a
> > 
> > for you to fetch changes up to c9638a65d7982b5069a500cc5c504e7a7faa2676:  
> 
> I get the following error when trying to push this from my scripts:
> 
> Commit: 50cda7cc4ab1 ("counter: fix docum. build problems after filename change")
> 	Fixes tag: Fixes: d70e46af7531 ("counter: Internalize sysfs interface code")
> 	Has these problem(s):
> 	        - Target SHA1 does not exist
> 
> Was this caused by rebasing?
> 
> thanks,
> 
> greg k-h

Almost certainly.  I remember checking the IIO pull but guess I forgot to run
the test script on the Counter one.  Will tidy up and resend.

Thanks,

Jonathan

  reply	other threads:[~2021-10-18 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-17 10:27 [PULL] 1st set of counter subsystem new features for the 5.16 cycle Jonathan Cameron
2021-10-18 15:45 ` Greg KH
2021-10-18 15:48   ` Jonathan Cameron [this message]
2021-10-18 17:58     ` Jonathan Cameron

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=20211018164846.0000470b@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --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.