Linux IIO development
 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 V3] 1st set of IIO new device support, features and cleanup for  the 5.16 cycle
Date: Tue, 19 Oct 2021 08:42:27 +0100	[thread overview]
Message-ID: <20211019084227.475ecdb0@jic23-huawei> (raw)
In-Reply-To: <YW5v6OPgC84X73Qg@kroah.com>

On Tue, 19 Oct 2021 09:12:40 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:

> On Mon, Oct 18, 2021 at 07:23:51PM +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/iio-for-5.16a-split-take3  
> 
> Almost :(
> 
> I get the following error from my scripts:
> 
> Commit: 4862202a0171 ("dt-bindings: iio: magnetometer: asahi-kasei,ak8975 add vid reg")
> 	Fixes tag: Fixes: 7e000fbff7a0 ("dt-bindings: iio: magnetometer: ak8975: convert format to yaml, add maintainer")
> 	Has these problem(s):
> 	        - empty lines surround the Fixes tag
> 
> Also, there was a merge conflict in drivers/iio/adc/aspeed_adc.c, but
> that was easy for me to resolve.
> 
> thanks,
> 
> greg k-h

Sigh.

The version of your scripts I have doesn't check for that particular one.
Anywhere I can get a newer version from?

V4 sent out. *crosses fingers*  Naturally the commit above was early
in the series so I had to fix all the other fixes tags again.

Thanks,

Jonathan

  reply	other threads:[~2021-10-19  7:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 18:23 [PULL V3] 1st set of IIO new device support, features and cleanup for the 5.16 cycle Jonathan Cameron
2021-10-19  7:12 ` Greg KH
2021-10-19  7:42   ` Jonathan Cameron [this message]
2021-10-19  9:43     ` Greg KH
2021-10-19  9:48       ` 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=20211019084227.475ecdb0@jic23-huawei \
    --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