From: Jonathan Cameron <jic23@kernel.org>
To: Christian Hewitt <christianshewitt@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-iio@vger.kernel.org,
devicetree <devicetree@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
AML <linux-amlogic@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 2/2] iio: adc: meson: add support for the GXLX SoC
Date: Sat, 8 Jun 2024 18:31:46 +0100 [thread overview]
Message-ID: <20240608183146.2a71572f@jic23-huawei> (raw)
In-Reply-To: <1E90764E-5D50-496A-B4DC-3D3982392183@gmail.com>
On Wed, 5 Jun 2024 07:15:58 +0400
Christian Hewitt <christianshewitt@gmail.com> wrote:
> > On 4 Jun 2024, at 1:10 PM, kernel test robot <lkp@intel.com> wrote:
> >
> > kernel test robot noticed the following build errors:
>
> Apologies. Build errors are because I wrongly imagined this dependent series from Martin to be merged:
>
> https://patchwork.kernel.org/project/linux-arm-kernel/cover/20240323231309.415425-1-martin.blumenstingl@googlemail.com/
>
> To be continued!
Given that was a case of not going to right mailing list, if you want
(and Martin doesn't have time) it is fine to pick that up and send it
a single series with your changes.
Thanks,
Jonathan
>
> Christian
>
>
prev parent reply other threads:[~2024-06-08 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240604055431.3313961-2-christianshewitt@gmail.com>
2024-06-04 9:10 ` [PATCH 2/2] iio: adc: meson: add support for the GXLX SoC kernel test robot
2024-06-05 3:15 ` Christian Hewitt
2024-06-08 17:31 ` 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=20240608183146.2a71572f@jic23-huawei \
--to=jic23@kernel.org \
--cc=christianshewitt@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@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).