From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL] Second set of features and cleanup for IIO in the 5.10 cycle.
Date: Mon, 21 Sep 2020 20:05:34 +0100 [thread overview]
Message-ID: <20200921200534.0e2b32fb@archlinux> (raw)
In-Reply-To: <20200921185230.GA1429057@kroah.com>
On Mon, 21 Sep 2020 20:52:30 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:
> On Mon, Sep 21, 2020 at 07:08:08PM +0100, Jonathan Cameron wrote:
> > The following changes since commit 2f0472a1f80e6230f126aa0af76e89f85abc37bd:
> >
> > drivers/iio/humidity/hdc2010.c:305:2-3: Unneeded semicolon (2020-09-06 16:05:56 +0100)
> >
> > are available in the Git repository at:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-5.10b
> >
> > for you to fetch changes up to eda7a4890f5825f1a01d635ab25235f4dacb8715:
> >
> > dt-bindings: iio: vishay,vcnl4000: add interrupts property (2020-09-21 18:54:26 +0100)
>
> So close:
>
> Commit: 7bf38af6540e ("iio:accel:bma180: Fix use of true when should be iio_shared_by enum")
> Fixes tag: Fixes: fdadbce0da4 ("iio: add Bosch BMA180 acceleration sensor driver")
> Has these problem(s):
> - SHA1 should be at least 12 digits long
> Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
> or later) just making sure it is not set (or set to "auto").
>
> One more digit! :)
>
> can you fix that up and resend?
>
> Remember, if I don't catch these, linux-next will...
Gah. I really need to take the time to get scripts in place for this rather
than always thinking I'll sort it next time and just eyeball them this
time.
False laziness gets me again. Sorry about that!
Thanks,
Jonathan
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2020-09-21 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 18:08 [PULL] Second set of features and cleanup for IIO in the 5.10 cycle Jonathan Cameron
2020-09-21 18:52 ` Greg KH
2020-09-21 19:05 ` 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=20200921200534.0e2b32fb@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;
as well as URLs for NNTP newsgroup(s).