From: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: renesas/sh73a0: use rdev_get_drvdata()
Date: Thu, 2 May 2024 14:40:40 +0200 [thread overview]
Message-ID: <ZjOJyGQE1ze2WXh8@qmqm.qmqm.pl> (raw)
In-Reply-To: <CAMuHMdUy+e1vQRBUfo2paBJi4pro-tKf9hOe3YaddcB=OtRfJw@mail.gmail.com>
On Thu, May 02, 2024 at 09:56:39AM +0200, Geert Uytterhoeven wrote:
> Hi Michal,
>
> On Wed, May 1, 2024 at 1:16 PM Michał Mirosław <mirq-linux@rere.qmqm.pl> wrote:
> > Replace `reg_data` access with the official wrapper. The field is going
> > away soon.
>
> Thanks for your patch!
>
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202404301218.URkWO6dj-lkp@intel.com/
>
> I am not sure these tags are needed, as the issue is not present in
> any tree yet?
>
> > Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Do you want me to pick this up (for v6.11), or do you want to queue
> this with the other patches from the series that removes reg_data?
> Please let me know.
> In case of the latter:
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
If you're ok with it going through the regulator tree, then I guess it
would be easier to manage as the series would build without observing
additional dependencies.
Best Regards
Michał Mirosław
prev parent reply other threads:[~2024-05-02 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 11:15 [PATCH] pinctrl: renesas/sh73a0: use rdev_get_drvdata() Michał Mirosław
2024-05-02 7:56 ` Geert Uytterhoeven
2024-05-02 12:40 ` Michał Mirosław [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=ZjOJyGQE1ze2WXh8@qmqm.qmqm.pl \
--to=mirq-linux@rere.qmqm.pl \
--cc=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.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 read-only IMAP folder(s) and NNTP newsgroup(s).