public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: linux-kernel@vger.kernel.org, josh@joshtriplett.org
Subject: Re: [PATCH RFC tip/core/rcu] Make SRCU be once again optional
Date: Fri, 2 Jun 2017 20:59:15 -0700	[thread overview]
Message-ID: <20170603035915.GA23375@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170512191005.GE3956@linux.vnet.ibm.com>

On Fri, May 12, 2017 at 12:10:05PM -0700, Paul E. McKenney wrote:
> On Fri, May 12, 2017 at 02:59:48PM -0400, Nicolas Pitre wrote:
> > On Fri, 12 May 2017, Paul E. McKenney wrote:

[ . . . ]

> > No.  "Available in mainline" is the name of the game for all I do. If it 
> > can't be made acceptable for mainline then it basically has no chance of 
> > gaining traction and becoming generally useful. My approach is therefore 
> > to always find solutions that can be maintained upstream and contributed 
> > to with minimal fuss by anyone.
> 
> OK, then wish me luck.  ;-)

And still quite a bit of back and forth.  How are things with tty?

One question that came up -- what sort of SoCs are you targeting?
A number of people are insisting that smartphone SoCs with 256M DRAM
are the minimal systems of the future.  This seems unlikely to me,
given the potential for extremely cheap SoCs with EDRAM or some such,
but figured I should ask what you are targeting.

							Thanx, Paul

  reply	other threads:[~2017-06-03  3:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28 21:15 [PATCH RFC tip/core/rcu] Make SRCU be once again optional Paul E. McKenney
2017-04-28 21:51 ` Nicolas Pitre
2017-04-29  0:10   ` Paul E. McKenney
2017-05-12 18:41     ` Paul E. McKenney
2017-05-12 18:45       ` Paul E. McKenney
2017-05-12 18:59       ` Nicolas Pitre
2017-05-12 19:10         ` Paul E. McKenney
2017-06-03  3:59           ` Paul E. McKenney [this message]
2017-06-03  5:18             ` Nicolas Pitre
2017-06-03 20:36               ` Paul E. McKenney
2018-01-16 21:02                 ` Arnd Bergmann
2018-01-16 21:10                   ` Arnd Bergmann
2018-01-16 22:34                   ` Paul E. McKenney
2018-01-16 22:55                     ` Arnd Bergmann
2018-01-16 23:03                       ` Arnd Bergmann
2018-01-16 23:57                         ` Paul E. McKenney
2018-01-17 10:29                           ` Arnd Bergmann
2018-01-17 16:32                             ` Josh Triplett
2018-01-17 17:10                               ` Arnd Bergmann
2018-01-17 16:47                             ` 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=20170603035915.GA23375@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.pitre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox