[GIT,PULL,6/7] ARM: tegra: Default configuration changes for v5.9-rc1
mbox series

Message ID 20200717161300.1661002-6-thierry.reding@gmail.com
State Mainlined, archived
Commit 3a3cb021b0380e2cbf7e1d158c37402874b54a9a
Headers show
Series
  • [GIT,PULL,1/7] dt-bindings: Changes for v5.9-rc1
Related show

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.9-arm-defconfig

Message

Thierry Reding July 17, 2020, 4:12 p.m. UTC
Hi ARM SoC maintainers,

The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:

  Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.9-arm-defconfig

for you to fetch changes up to 3a3cb021b0380e2cbf7e1d158c37402874b54a9a:

  ARM: tegra_defconfig: Enable options useful for Nexus 7 and Acer A500 (2020-07-16 14:22:41 +0200)

Thanks,
Thierry

----------------------------------------------------------------
ARM: tegra: Default configuration changes for v5.9-rc1

Enables a few new configuration options that are useful on the new Nexus
7 and Acer A500 devices, as well as the userspace CPU frequency governor
that's mainly used for testing.

----------------------------------------------------------------
Dmitry Osipenko (1):
      ARM: tegra_defconfig: Enable options useful for Nexus 7 and Acer A500

Jon Hunter (1):
      ARM: tegra: Enable CPUFREQ userspace governor

 arch/arm/configs/tegra_defconfig | 43 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 43 insertions(+)

Comments

Arnd Bergmann July 17, 2020, 7:24 p.m. UTC | #1
On Fri, Jul 17, 2020 at 6:13 PM Thierry Reding <thierry.reding@gmail.com> wrote:
> ARM: tegra: Default configuration changes for v5.9-rc1
>
> Enables a few new configuration options that are useful on the new Nexus
> 7 and Acer A500 devices, as well as the userspace CPU frequency governor
> that's mainly used for testing.

I've pulled all the other branches, but I'm a little bit wary about
this one since
Dmitry's patch enables a number of options that would increase the kernel
size, and I see no indication that it has been reviewed by anyone else.

I think the changes all make sense, but I would prefer to have a wider
audience for that patch and get some Acks. If you like, you can send the
tegra specific changes in a new pull request in the meantime, and then
send the remaining additions to the usual suspects as an RFC, with
Cc:soc@kernel.org, so I can apply it later if everyone is happy enough
with it.

      Arnd
Dmitry Osipenko July 17, 2020, 8:13 p.m. UTC | #2
17.07.2020 22:24, Arnd Bergmann пишет:
> On Fri, Jul 17, 2020 at 6:13 PM Thierry Reding <thierry.reding@gmail.com> wrote:
>> ARM: tegra: Default configuration changes for v5.9-rc1
>>
>> Enables a few new configuration options that are useful on the new Nexus
>> 7 and Acer A500 devices, as well as the userspace CPU frequency governor
>> that's mainly used for testing.
> 
> I've pulled all the other branches, but I'm a little bit wary about
> this one since
> Dmitry's patch enables a number of options that would increase the kernel
> size, and I see no indication that it has been reviewed by anyone else.
> 
> I think the changes all make sense, but I would prefer to have a wider
> audience for that patch and get some Acks. If you like, you can send the
> tegra specific changes in a new pull request in the meantime, and then
> send the remaining additions to the usual suspects as an RFC, with
> Cc:soc@kernel.org, so I can apply it later if everyone is happy enough
> with it.

Hello, Arnd!

But these are already the tegra specific changes. The patch changes
tegra_defconfig and not the multi_v7_defconfig.

Could you please clarify from whom would you expect to get more Acks if
not from the tegra maintainers?

In practice nobody uses upstream defconfig as-is, it's only used as
initial template. So I'm not sure why tegra-kernel size makes you to
worry. Could you please explain?
Arnd Bergmann July 17, 2020, 8:23 p.m. UTC | #3
On Fri, Jul 17, 2020 at 10:13 PM Dmitry Osipenko <digetx@gmail.com> wrote:
> 17.07.2020 22:24, Arnd Bergmann пишет:
> > On Fri, Jul 17, 2020 at 6:13 PM Thierry Reding <thierry.reding@gmail.com> wrote:
> >> ARM: tegra: Default configuration changes for v5.9-rc1
> >>
> >> Enables a few new configuration options that are useful on the new Nexus
> >> 7 and Acer A500 devices, as well as the userspace CPU frequency governor
> >> that's mainly used for testing.
> >
> > I've pulled all the other branches, but I'm a little bit wary about
> > this one since
> > Dmitry's patch enables a number of options that would increase the kernel
> > size, and I see no indication that it has been reviewed by anyone else.
> >
> > I think the changes all make sense, but I would prefer to have a wider
> > audience for that patch and get some Acks. If you like, you can send the
> > tegra specific changes in a new pull request in the meantime, and then
> > send the remaining additions to the usual suspects as an RFC, with
> > Cc:soc@kernel.org, so I can apply it later if everyone is happy enough
> > with it.
>
> Hello, Arnd!
>
> But these are already the tegra specific changes. The patch changes
> tegra_defconfig and not the multi_v7_defconfig.
>
> Could you please clarify from whom would you expect to get more Acks if
> not from the tegra maintainers?
>
> In practice nobody uses upstream defconfig as-is, it's only used as
> initial template. So I'm not sure why tegra-kernel size makes you to
> worry. Could you please explain?

It was a mistake on my end, for some reason I thought you were
changing the arm64 defconfig, which does not have per-platform
files.

The patch is good, and I'll pull the branch as soon as I get to it
(it's a bit late for today).

      Arnd
Dmitry Osipenko July 17, 2020, 8:25 p.m. UTC | #4
17.07.2020 23:23, Arnd Bergmann пишет:
> On Fri, Jul 17, 2020 at 10:13 PM Dmitry Osipenko <digetx@gmail.com> wrote:
>> 17.07.2020 22:24, Arnd Bergmann пишет:
>>> On Fri, Jul 17, 2020 at 6:13 PM Thierry Reding <thierry.reding@gmail.com> wrote:
>>>> ARM: tegra: Default configuration changes for v5.9-rc1
>>>>
>>>> Enables a few new configuration options that are useful on the new Nexus
>>>> 7 and Acer A500 devices, as well as the userspace CPU frequency governor
>>>> that's mainly used for testing.
>>>
>>> I've pulled all the other branches, but I'm a little bit wary about
>>> this one since
>>> Dmitry's patch enables a number of options that would increase the kernel
>>> size, and I see no indication that it has been reviewed by anyone else.
>>>
>>> I think the changes all make sense, but I would prefer to have a wider
>>> audience for that patch and get some Acks. If you like, you can send the
>>> tegra specific changes in a new pull request in the meantime, and then
>>> send the remaining additions to the usual suspects as an RFC, with
>>> Cc:soc@kernel.org, so I can apply it later if everyone is happy enough
>>> with it.
>>
>> Hello, Arnd!
>>
>> But these are already the tegra specific changes. The patch changes
>> tegra_defconfig and not the multi_v7_defconfig.
>>
>> Could you please clarify from whom would you expect to get more Acks if
>> not from the tegra maintainers?
>>
>> In practice nobody uses upstream defconfig as-is, it's only used as
>> initial template. So I'm not sure why tegra-kernel size makes you to
>> worry. Could you please explain?
> 
> It was a mistake on my end, for some reason I thought you were
> changing the arm64 defconfig, which does not have per-platform
> files.
> 
> The patch is good, and I'll pull the branch as soon as I get to it
> (it's a bit late for today).

Awesome, thank you!