From: Linus Walleij <linus.walleij@linaro.org>
To: Chester Lin <clin@suse.com>
Cc: "Andy Shevchenko" <andy.shevchenko@gmail.com>,
"NXP S32 Linux Team" <s32@nxp.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Ghennadi Procopciuc" <Ghennadi.Procopciuc@oss.nxp.com>,
"Andrei Stefanescu" <andrei.stefanescu@nxp.com>,
"Radu Pirea" <radu-nicolae.pirea@nxp.com>,
"Andreas Färber" <afaerber@suse.de>,
"Matthias Brugger" <mbrugger@suse.com>
Subject: Re: [PATCH v5 2/5] pinctrl: s32cc: refactor pin config parsing
Date: Mon, 27 Mar 2023 23:35:20 +0200 [thread overview]
Message-ID: <CACRpkdat=069ZyPL=w1_z6cNZ4EbVvG==SLcnT-pmsH6zhqtpQ@mail.gmail.com> (raw)
In-Reply-To: <20230327062754.3326-3-clin@suse.com>
On Mon, Mar 27, 2023 at 8:28 AM Chester Lin <clin@suse.com> wrote:
> Move common codes into smaller inline functions and remove argument checks
> that are not actually used by pull up/down bits in the S32 MSCR register.
>
> Signed-off-by: Chester Lin <clin@suse.com>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Patch applied!
Yours,
Linus Walleij
next prev parent reply other threads:[~2023-03-27 21:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 6:27 [PATCH v5 0/5] pinctrl: s32: driver improvements and generic struct use Chester Lin
2023-03-27 6:27 ` [PATCH v5 1/5] pinctrl: s32: refine error/return/config checks and simplify driver codes Chester Lin
2023-03-27 21:34 ` Linus Walleij
2023-03-27 6:27 ` [PATCH v5 2/5] pinctrl: s32cc: refactor pin config parsing Chester Lin
2023-03-27 21:35 ` Linus Walleij [this message]
2023-03-27 6:27 ` [PATCH v5 3/5] pinctrl: s32cc: embed generic struct pingroup Chester Lin
2023-03-27 21:36 ` Linus Walleij
2023-03-27 6:27 ` [PATCH v5 4/5] pinctrl: s32cc: Use generic struct data to describe pin function Chester Lin
2023-03-27 6:27 ` [PATCH v5 5/5] pinctrl: s32: separate const device data from struct s32_pinctrl_soc_info Chester Lin
2023-03-27 11:58 ` Andy Shevchenko
2023-03-27 21:39 ` Linus Walleij
2023-03-29 4:25 ` Chester Lin
2023-03-29 4:16 ` [RESEND PATCH " Chester Lin
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='CACRpkdat=069ZyPL=w1_z6cNZ4EbVvG==SLcnT-pmsH6zhqtpQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=Ghennadi.Procopciuc@oss.nxp.com \
--cc=afaerber@suse.de \
--cc=andrei.stefanescu@nxp.com \
--cc=andy.shevchenko@gmail.com \
--cc=clin@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=radu-nicolae.pirea@nxp.com \
--cc=s32@nxp.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).