From: Christoph Hellwig <hch@lst.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Christoph Hellwig" <hch@lst.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Christian Brauner" <brauner@kernel.org>,
"Hridya Valsaraju" <hridya@google.com>,
"Suren Baghdasaryan" <surenb@google.com>,
"Theodore Ts'o" <tytso@mit.edu>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>,
"Paolo Abeni" <pabeni@redhat.com>,
"Rob Herring" <robh@kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Neeraj Upadhyay" <quic_neeraju@quicinc.com>,
"Josh Triplett" <josh@joshtriplett.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Lai Jiangshan" <jiangshanlai@gmail.com>,
"Shuah Khan" <shuah@kernel.org>,
linux-kernel@vger.kernel.org, wireguard@lists.zx2c4.com,
netdev@vger.kernel.org, rcu@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] remove CONFIG_ANDROID
Date: Wed, 29 Jun 2022 18:30:07 +0200 [thread overview]
Message-ID: <20220629163007.GA25279@lst.de> (raw)
In-Reply-To: <Yrx8/Fyx15CTi2zq@zx2c4.com>
On Wed, Jun 29, 2022 at 06:25:32PM +0200, Jason A. Donenfeld wrote:
> Anyway, instead of the slow drip of "facts" and ≤three sentence emails,
> can you just write up a paragraph that indicates this is safe to do (for
> both (1) and (2)) in your v+1?
Why would I care? If your config wakeups up so often that you need
special casing find a way to deal with it. In the upstream kernel
CONFIG_ANDROID is a very strong indicator for a desktop kernel as
that is much more common than someone actually running upstream Linux
on one of the very few Android devices actually fully supported by
upstream Linux.
next prev parent reply other threads:[~2022-06-29 23:30 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 15:01 Christoph Hellwig
2022-06-29 15:01 ` [PATCH] " Christoph Hellwig
2022-06-29 15:27 ` Greg Kroah-Hartman
2022-06-29 16:07 ` Paul E. McKenney
2022-06-29 16:09 ` Jason A. Donenfeld
2022-06-29 16:10 ` Christoph Hellwig
2022-06-29 16:13 ` Jason A. Donenfeld
2022-06-29 16:15 ` Christoph Hellwig
2022-06-29 16:25 ` Jason A. Donenfeld
2022-06-29 16:30 ` Christoph Hellwig [this message]
2022-06-29 16:38 ` Jason A. Donenfeld
2022-06-29 16:45 ` Christoph Hellwig
2022-06-29 16:52 ` Jason A. Donenfeld
2022-06-29 17:00 ` Greg Kroah-Hartman
2022-06-29 17:10 ` Jason A. Donenfeld
2022-06-29 17:19 ` Greg Kroah-Hartman
2022-06-29 17:30 ` Jason A. Donenfeld
2022-06-29 17:35 ` Christoph Hellwig
2022-06-29 17:42 ` Jason A. Donenfeld
2022-06-29 18:59 ` Paul E. McKenney
2022-06-29 16:56 ` Steven Rostedt
2022-06-29 17:19 ` Jason A. Donenfeld
2022-06-29 17:34 ` Jason A. Donenfeld
2022-06-29 19:05 ` Kalesh Singh
2022-06-29 19:41 ` Theodore Ts'o
2022-06-29 20:47 ` Jason A. Donenfeld
2022-06-29 22:26 ` Kalesh Singh
2022-06-29 23:02 ` Jason A. Donenfeld
2022-06-29 23:19 ` Kalesh Singh
2022-06-30 0:36 ` Joe Perches
2022-06-30 0:50 ` Jason A. Donenfeld
2022-06-30 1:44 ` Joe Perches
2022-06-30 3:02 ` Jason A. Donenfeld
2022-06-29 23:52 ` John Stultz
2022-06-30 0:24 ` Jason A. Donenfeld
2022-06-30 0:30 ` Jason A. Donenfeld
2022-06-30 4:25 ` Kalesh Singh
2022-06-30 10:05 ` Jason A. Donenfeld
2022-06-30 17:12 ` John Stultz
2022-06-30 17:24 ` Jason A. Donenfeld
2022-07-01 20:22 ` Jonathan Corbet
2022-07-01 20:53 ` Jason A. Donenfeld
2022-06-29 16:34 ` Paul E. McKenney
2022-06-29 16:37 ` Christoph Hellwig
2022-06-29 16:45 ` Jason A. Donenfeld
2022-06-29 17:04 ` Paul E. McKenney
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=20220629163007.GA25279@lst.de \
--to=hch@lst.de \
--cc=Jason@zx2c4.com \
--cc=alex_y_xu@yahoo.ca \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hridya@google.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maco@android.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=tytso@mit.edu \
--cc=wireguard@lists.zx2c4.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).