From: Arnd Bergmann <arnd@kernel.org>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
SoC Team <soc@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Ulf Hansson <ulf.hansson@linaro.org>,
"open list:TEGRA ARCHITECTURE SUPPORT"
<linux-tegra@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: tegra: add regulator dependency
Date: Wed, 21 Jul 2021 21:59:28 +0200 [thread overview]
Message-ID: <CAK8P3a0PFcEk5T7Ym+u+8PuWEyyZoZPkv5S5uP-mrBZ4NDZf0A@mail.gmail.com> (raw)
In-Reply-To: <c9968f90-0633-9467-a3fb-725b92116fe2@gmail.com>
On Wed, Jul 21, 2021 at 5:29 PM Dmitry Osipenko <digetx@gmail.com> wrote:
> 21.07.2021 18:14, Arnd Bergmann пишет:
>
> [1]
> https://patchwork.ozlabs.org/project/linux-tegra/patch/20210621160739.22448-1-digetx@gmail.com/
>
> It looks like my variant of the fix should be a bit more correct since
> it won't build the regulator drivers if both TEGRA=n and REGULATOR=n.
>
> I guess it should be fine if you could take the patch directly, perhaps
> Jon could ack the patch for that. Otherwise we could wait for Thierry to
> return.
Sounds good to me. Please send your patch to soc@kernel.org (with everyone
on Cc) so it lands in our patchwork, and if Jon or Thierry acks it that makes it
there as well.
Arnd
next prev parent reply other threads:[~2021-07-21 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 15:14 [PATCH] arm64: tegra: add regulator dependency Arnd Bergmann
2021-07-21 15:29 ` Dmitry Osipenko
2021-07-21 19:59 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-21 15:13 Arnd Bergmann
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=CAK8P3a0PFcEk5T7Ym+u+8PuWEyyZoZPkv5S5uP-mrBZ4NDZf0A@mail.gmail.com \
--to=arnd@kernel.org \
--cc=arnd@arndb.de \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=soc@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.