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 new device support, cleanups and yaml conversions for the 5.11 cycle
Date: Thu, 3 Dec 2020 19:20:29 +0100 [thread overview]
Message-ID: <X8ksbapSAzhum4V6@kroah.com> (raw)
In-Reply-To: <20201202130752.530970c6@archlinux>
On Wed, Dec 02, 2020 at 01:07:52PM +0000, Jonathan Cameron wrote:
> The following changes since commit 749c1e1481e1d242ded9dd1bf210ddb7c0d22a4f:
>
> Merge tag 'iio-for-5.11a' of https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next (2020-11-24 08:30:08 +0100)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-5.11b
I get the following errors when pulling this. You seem to have not
signed off on two patches:
Commit 474830eb350d ("dt-bindings:iio:adc:remove atmel, adc-res and atmel, adc-res-names")
committer Signed-off-by missing
author email: alexandre.belloni@bootlin.com
committer email: Jonathan.Cameron@huawei.com
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Commit 38829b4e5a07 ("iio: adc: ad7298: check regulator for null in ad7298_get_ref_voltage()")
committer Signed-off-by missing
author email: alexandru.ardelean@analog.com
committer email: Jonathan.Cameron@huawei.com
Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
If I took these, you would get the same warnings from linux-next, but
without the ability to fix them up :(
thanks,
greg k-h
prev parent reply other threads:[~2020-12-03 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 13:07 [PULL] 2nd set of IIO new device support, cleanups and yaml conversions for the 5.11 cycle Jonathan Cameron
2020-12-03 18:20 ` Greg KH [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=X8ksbapSAzhum4V6@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.