From: Joel Stanley <joel@jms.id.au>
To: Quan Nguyen <quan@os.amperecomputing.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
"Thang Q . Nguyen" <thang@os.amperecomputing.com>,
Open Source Submission <patches@amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>
Subject: Re: [PATCH linux dev-5.15 0/5] Enable second flash, update gpios pin and merge adc channels
Date: Thu, 18 Aug 2022 07:41:50 +0000 [thread overview]
Message-ID: <CACPK8XdAUxSszm9-5Sugn7=m_Km-dcBH0_otLwfpVr7Db8Y_XA@mail.gmail.com> (raw)
In-Reply-To: <f6c87af2-827f-7451-fe30-7ec1b62e5cee@os.amperecomputing.com>
On Thu, 18 Aug 2022 at 07:33, Quan Nguyen <quan@os.amperecomputing.com> wrote:
>
> Dear Joel,
>
> Could you help review and backport this patch series to dev-5.15 branch?
>
> https://lore.kernel.org/linux-arm-kernel/20220228000242.1884-1-quan@os.amperecomputing.com/
Thanks for the reminder. That's done now.
Cheers,
Joel
prev parent reply other threads:[~2022-08-18 7:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 0:02 [PATCH v1 0/5] Enable second flash, update gpios pin and merge adc channels Quan Nguyen
2022-02-28 0:02 ` [PATCH v1 1/5] ARM: dts: aspeed: mtjade: Enable secondary flash Quan Nguyen
2022-02-28 0:02 ` [PATCH v1 2/5] ARM: dts: aspeed: mtjade: Update rtc-battery-voltage-read-enable pin Quan Nguyen
2022-02-28 0:02 ` [PATCH v1 3/5] ARM: dts: aspeed: mtjade: Update host0-ready pin Quan Nguyen
2022-02-28 0:02 ` [PATCH v1 4/5] ARM: dts: aspeed: mtjade: Rename GPIO hog nodes to match schema Quan Nguyen
2022-02-28 0:02 ` [PATCH v1 5/5] ARM: dts: aspeed: mtjade: Move all adc sensors into iio-hwmon node Quan Nguyen
2022-02-28 4:21 ` [PATCH v1 0/5] Enable second flash, update gpios pin and merge adc channels Joel Stanley
2022-02-28 11:13 ` Quan Nguyen
2022-07-06 4:21 ` Quan Nguyen
2022-08-18 7:32 ` [PATCH linux dev-5.15 " Quan Nguyen
2022-08-18 7:41 ` Joel Stanley [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='CACPK8XdAUxSszm9-5Sugn7=m_Km-dcBH0_otLwfpVr7Db8Y_XA@mail.gmail.com' \
--to=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=quan@os.amperecomputing.com \
--cc=thang@os.amperecomputing.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).