From: Stephen Boyd <swboyd@chromium.org>
To: Felix Fietkau <nbd@nbd.name>,
Matthias Brugger <matthias.bgg@gmail.com>,
soc@kernel.org
Cc: linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v10 0/6] Clock and PCIe support for Airoha EN7523 SoC
Date: Tue, 15 Mar 2022 16:44:27 -0700 [thread overview]
Message-ID: <CAE-0n50tDVmQnruVy5cvseQrH9dWjHWr7qAoLwDnAL=oS9AEzw@mail.gmail.com> (raw)
In-Reply-To: <20220314084409.84394-1-nbd@nbd.name>
Quoting Felix Fietkau (2022-03-14 01:44:02)
> This patchset adds the remaining patches needed from the last Airoha EN7523
> SoC support series
Please add a changelog here, preferably with lore links to previous
revisions. It helps folks recall the patch series.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-03-15 23:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 8:44 [PATCH v10 0/6] Clock and PCIe support for Airoha EN7523 SoC Felix Fietkau
2022-03-14 8:44 ` [PATCH v10 1/6] dt-bindings: Add en7523-scu device tree binding documentation Felix Fietkau
2022-04-23 2:12 ` Stephen Boyd
2022-04-23 2:13 ` Stephen Boyd
2022-03-14 8:44 ` [PATCH v10 2/6] clk: en7523: Add clock driver for Airoha EN7523 SoC Felix Fietkau
2022-03-15 16:34 ` Matthias Brugger
2022-04-23 2:13 ` Stephen Boyd
2022-03-14 8:44 ` [PATCH v10 3/6] ARM: dts: add clock support for Airoha EN7523 Felix Fietkau
2022-04-25 11:51 ` Matthias Brugger
2022-03-14 8:44 ` [PATCH v10 4/6] dt-bindings: PCI: Add support for Airoha EN7532 Felix Fietkau
2022-03-14 8:44 ` [PATCH v10 5/6] PCI: mediatek: Allow building for ARCH_AIROHA Felix Fietkau
2022-03-14 8:44 ` [PATCH v10 6/6] ARM: dts: Add PCIe support for Airoha EN7523 Felix Fietkau
2022-03-15 23:44 ` Stephen Boyd [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='CAE-0n50tDVmQnruVy5cvseQrH9dWjHWr7qAoLwDnAL=oS9AEzw@mail.gmail.com' \
--to=swboyd@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=soc@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).