From: Brian Masney <bmasney@redhat.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: kernel test robot <lkp@intel.com>,
jic23@kernel.org, llvm@lists.linux.dev,
oe-kbuild-all@lists.linux.dev, andriy.shevchenko@linux.intel.com,
trix@redhat.com, lars@metafoo.de, nathan@kernel.org,
ndesaulniers@google.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, hslester96@gmail.com
Subject: Re: [PATCH] iio: light: tsl2772: fix reading proximity-diodes from device tree
Date: Tue, 4 Apr 2023 18:36:53 -0400 [thread overview]
Message-ID: <ZCymhaDkRkfzk2kP@x1> (raw)
In-Reply-To: <20230404123544.6m5juesxwf4tklkm@pengutronix.de>
On Tue, Apr 04, 2023 at 02:35:44PM +0200, Uwe Kleine-König wrote:
> Hello Brian,
>
> On Tue, Apr 04, 2023 at 07:13:03AM -0400, Brian Masney wrote:
> > This doesn't contain the code that's in iio/togreg [1], and that's why
> > the build failed. I originally developed / built this against
> > next-20230330. I just checked linus/master, next-20230404, iio/testing,
> > and all have the expected code that defines prox_diode_mask.
> >
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/tree/drivers/iio/light/tsl2772.c?h=togreg#n593
>
> You might want to make use of the --base parameter to git format-patch
> for you next submission. With that the auto builders have a chance to
> test on the right tree.
I'll add the --base parameter next time. However, I think the issue is
that this compiler error is triggered by this patch [1] that's not in
any maintainer trees. I suspect the kernel test robot still has that in
it's local tree from a previous round of testing against this driver.
[1] https://lore.kernel.org/lkml/20230327120823.1369700-1-trix@redhat.com/
Brian
next prev parent reply other threads:[~2023-04-04 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 1:14 [PATCH] iio: light: tsl2772: fix reading proximity-diodes from device tree Brian Masney
2023-04-04 7:13 ` kernel test robot
2023-04-04 11:13 ` Brian Masney
2023-04-04 12:35 ` Uwe Kleine-König
2023-04-04 22:36 ` Brian Masney [this message]
2023-04-08 9:47 ` 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=ZCymhaDkRkfzk2kP@x1 \
--to=bmasney@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hslester96@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=trix@redhat.com \
--cc=u.kleine-koenig@pengutronix.de \
/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.