linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	Thierry Reding
	<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: arm-soc <arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	SoC Team <soc-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	"open list:TEGRA ARCHITECTURE SUPPORT"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux ARM
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [GIT PULL 6/7] ARM: tegra: Default configuration changes for v5.9-rc1
Date: Fri, 17 Jul 2020 23:13:41 +0300	[thread overview]
Message-ID: <a6f83a03-3a8f-47d0-6770-fe0e2595cde5@gmail.com> (raw)
In-Reply-To: <CAK8P3a1niUF7xK_bmz=8NJbRGxs7iFzNnRgRS9H=bXpMqarsWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

17.07.2020 22:24, Arnd Bergmann пишет:
> On Fri, Jul 17, 2020 at 6:13 PM Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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?

  parent reply	other threads:[~2020-07-17 20:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 16:12 [GIT PULL 1/7] dt-bindings: Changes for v5.9-rc1 Thierry Reding
     [not found] ` <20200717161300.1661002-1-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-17 16:12   ` [GIT PULL 2/7] firmware: tegra: " Thierry Reding
2020-07-17 16:12   ` [GIT PULL 3/7] memory: " Thierry Reding
2020-07-17 16:12   ` [GIT PULL 4/7] soc/tegra: " Thierry Reding
2020-07-17 16:12   ` [GIT PULL 5/7] ARM: tegra: Device tree changes " Thierry Reding
     [not found]     ` <20200717161300.1661002-5-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-17 19:20       ` Arnd Bergmann
2020-07-17 16:12   ` [GIT PULL 6/7] ARM: tegra: Default configuration " Thierry Reding
     [not found]     ` <20200717161300.1661002-6-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-17 19:24       ` Arnd Bergmann
     [not found]         ` <CAK8P3a1niUF7xK_bmz=8NJbRGxs7iFzNnRgRS9H=bXpMqarsWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-07-17 20:13           ` Dmitry Osipenko [this message]
     [not found]             ` <a6f83a03-3a8f-47d0-6770-fe0e2595cde5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-17 20:23               ` Arnd Bergmann
     [not found]                 ` <CAK8P3a3nSYfotK=0ZL9XqeMi-v0nqxFZnFKy4OAbvnc9qzN8Xw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-07-17 20:25                   ` Dmitry Osipenko
2020-07-17 16:13   ` [GIT PULL 7/7] arm64: tegra: Device tree " Thierry Reding

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=a6f83a03-3a8f-47d0-6770-fe0e2595cde5@gmail.com \
    --to=digetx-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=soc-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).