From: Sjoerd Simons <sjoerd@collabora.com>
To: "Gregory CLEMENT" <gregory.clement@bootlin.com>,
"Marek Behún" <kabel@kernel.org>
Cc: kernel@collabora.com, Andrew Lunn <andrew@lunn.ch>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Moxtet bus fixes
Date: Mon, 18 Dec 2023 11:19:57 +0100 [thread overview]
Message-ID: <6c93241c35153cfb718db1d81e99e01bfb6dede5.camel@collabora.com> (raw)
In-Reply-To: <87fs03cyki.fsf@BL-laptop>
On Fri, 2023-12-15 at 15:47 +0100, Gregory CLEMENT wrote:
> Marek Behún <kabel@kernel.org> writes:
>
> > On Fri, 08 Dec 2023 15:51:20 +0100
> > Gregory CLEMENT <gregory.clement@bootlin.com> wrote:
> >
> > Gregory, as of yet I've never done a pull request. If you are
> > willing
> > to take all 3 patches now, please do. In the future I would like to
>
> OK I applied them on mvebu/driver.
Thanks both for moving this patches forward; Gregory looks like you
only applied two of the three patches (missing the dt patch), are you
expect that to flow through a different tree or ?
Regards,
--
Sjoerd Simons
Collabora Ltd.
next prev parent reply other threads:[~2023-12-18 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 21:35 [PATCH v2 0/3] Moxtet bus fixes Sjoerd Simons
2023-11-28 21:35 ` [PATCH v2 3/3] arm64: dts: armada-3720-turris-mox: set irq type for RTC Sjoerd Simons
2023-12-07 14:43 ` Marek Behún
2023-12-08 14:51 ` [PATCH v2 0/3] Moxtet bus fixes Gregory CLEMENT
2023-12-08 15:17 ` Marek Behún
2023-12-15 14:47 ` Gregory CLEMENT
2023-12-15 15:16 ` Sjoerd Simons
2023-12-18 10:19 ` Sjoerd Simons [this message]
2023-12-20 13:55 ` Gregory CLEMENT
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=6c93241c35153cfb718db1d81e99e01bfb6dede5.camel@collabora.com \
--to=sjoerd@collabora.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kabel@kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
/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).