From: Andreas Kemnade <andreas@kemnade.info>
To: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
lee.jones@linaro.org, b.galvani@gmail.com,
linus.walleij@linaro.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, phh@phh.me, stefan@agner.ch,
letux-kernel@openphoenux.org, jic23@kernel.org
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v5 2/2] iio: adc: rn5t618: Add ADC driver for RN5T618/RC5T619
Date: Wed, 26 Feb 2020 20:27:19 +0100 [thread overview]
Message-ID: <20200226202719.46ce9600@kemnade.info> (raw)
In-Reply-To: <20200223131638.12130-3-andreas@kemnade.info>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
Hi,
On Sun, 23 Feb 2020 14:16:38 +0100
Andreas Kemnade <andreas@kemnade.info> wrote:
> + if (rn5t618->irq_data)
> + adc->irq = regmap_irq_get_virq(rn5t618->irq_data,
> + RN5T618_IRQ_ADC);
> +
RN5T618_IRQ_ADC is defined in the RTC patchset mentioned as dependency,
which adds IRQ support and I am asked to rebase it on top of plain mainline.
Does that mean that the kernel git source does not need to be bisectable
anymore?
Regards,
Andreas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-02-26 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 13:16 [PATCH v5 0/2] mfd: rn5t618: add ADC support Andreas Kemnade
2020-02-23 13:16 ` [PATCH v5 1/2] mfd: rn5t618: add ADC subdevice for RC5T619 Andreas Kemnade
2020-02-26 15:40 ` Lee Jones
2020-02-26 16:49 ` Andreas Kemnade
2020-02-26 17:46 ` Lee Jones
2020-02-26 18:11 ` Andreas Kemnade
2020-02-27 9:40 ` Lee Jones
2020-02-27 11:56 ` Andreas Kemnade
2020-02-23 13:16 ` [PATCH v5 2/2] iio: adc: rn5t618: Add ADC driver for RN5T618/RC5T619 Andreas Kemnade
2020-02-26 19:27 ` Andreas Kemnade [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=20200226202719.46ce9600@kemnade.info \
--to=andreas@kemnade.info \
--cc=Jonathan.Cameron@huawei.com \
--cc=b.galvani@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=letux-kernel@openphoenux.org \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phh@phh.me \
--cc=pmeerw@pmeerw.net \
--cc=stefan@agner.ch \
/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