From: Linus Walleij <linus.walleij@linaro.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: sean.wang@kernel.org, matthias.bgg@gmail.com,
linux-mediatek@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@collabora.com,
wenst@chromium.org
Subject: Re: [PATCH v2 0/5] MediaTek pinctrl drivers cleanups
Date: Thu, 17 Mar 2022 02:07:43 +0100 [thread overview]
Message-ID: <CACRpkdZnz9ry74mGZ-SvxvVt0NOZMpjGVL3KayK+xRXgRKSQPg@mail.gmail.com> (raw)
In-Reply-To: <a06003ae-2dcc-f5a4-3b5c-62db99d18950@collabora.com>
On Wed, Mar 16, 2022 at 11:57 AM AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com> wrote:
> Hello maintainers,
>
> friendly ping for this series that already got a Reviewed-by tag on all patches :)
Patches applied!
Sorry for missing them in yesterdays batch.
Yours,
Linus Walleij
_______________________________________________
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-17 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 11:11 [PATCH v2 0/5] MediaTek pinctrl drivers cleanups AngeloGioacchino Del Regno
2022-02-22 11:11 ` [PATCH v2 1/5] pinctrl: mediatek: paris: Unify probe function by using OF match data AngeloGioacchino Del Regno
2022-02-22 11:11 ` [PATCH v2 2/5] pinctrl: mediatek: common-v1: Add common probe function AngeloGioacchino Del Regno
2022-02-22 11:11 ` [PATCH v2 3/5] pinctrl: mediatek: common-v1: Use " AngeloGioacchino Del Regno
2022-02-22 11:11 ` [PATCH v2 4/5] pinctrl: mediatek: common-v1: Commonize spec_pupd callback AngeloGioacchino Del Regno
2022-02-22 11:11 ` [PATCH v2 5/5] pinctrl: mediatek: common-v1: Commonize spec_ies_smt_set callback AngeloGioacchino Del Regno
2022-03-16 10:57 ` [PATCH v2 0/5] MediaTek pinctrl drivers cleanups AngeloGioacchino Del Regno
2022-03-17 1:07 ` Linus Walleij [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=CACRpkdZnz9ry74mGZ-SvxvVt0NOZMpjGVL3KayK+xRXgRKSQPg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@kernel.org \
--cc=wenst@chromium.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).