public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: rdunlap@xenotime.net, harvey.harrison@gmail.com,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	randy.dunlap@oracle.com
Subject: Re: [PATCH] mfd: kconfig exposing unbuildable driver
Date: Tue, 22 Apr 2008 23:02:38 -0700	[thread overview]
Message-ID: <20080422230238.48c50ea0.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080422210153.GB21435@flint.arm.linux.org.uk>

> On Tue, 22 Apr 2008 22:01:53 +0100 Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> On Tue, Apr 22, 2008 at 01:47:18PM -0700, Randy.Dunlap wrote:
> > On Tue, 22 Apr 2008, Russell King wrote:
> > > On Tue, Apr 22, 2008 at 01:38:28PM -0700, Randy.Dunlap wrote:
> > > > On Tue, 22 Apr 2008, Russell King wrote:
> > > > 
> > > > > That was my initial approach as well, which got shot down by Andrew
> > > > > Morton and others as being unacceptable.
> > > > 
> > > > where?
> > > 
> > > In private mail.
> > > 
> > > > why?
> > > 
> > > Well, first I need to gain the permission of Andrew to post his private
> > > message.  I'm not being subborn here - I _do_ _not_ reproduce private
> > > messages in public without prior permission.
> > 
> > Sure, understood.
> > 
> > > > Seems like we need to push back on that part.
> > > 
> > > Talk to Andrew then.
> > 
> > He is cc-ed (although traveling much this week IIRC).
> 
> In which case, since it's likely I won't get a reply in the next hour
> (which'll delay my response by 24 hours) let me paraphrase what Andrew
> said.
> 
> Andrew believes that it is beneficial to have other architectures,
> particularly x86, build other architectures drivers.

Well.  I pointed out that there are arguments either way, and I do tend to
think that the let-x86-compile-it-too approach is perhaps the better one,
but that's a 51%/49% opinion.  Others disagree and lots and lots of code
has gone the other way.  Do whatever you think best ;)


  parent reply	other threads:[~2008-04-23  6:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 20:25 [PATCH] mfd: kconfig exposing unbuildable driver Harvey Harrison
2008-04-22 20:33 ` Russell King
2008-04-22 20:38   ` Randy.Dunlap
2008-04-22 20:45     ` Russell King
2008-04-22 20:47       ` Randy.Dunlap
2008-04-22 21:01         ` Russell King
2008-04-22 21:06           ` Randy Dunlap
2008-04-23  6:02           ` Andrew Morton [this message]
2008-04-22 21:05   ` Linus Torvalds
2008-04-22 21:36     ` Russell King
2008-04-22 21:47       ` Linus Torvalds
2008-04-23 20:14     ` pHilipp Zabel
2008-04-23 20:02   ` pHilipp Zabel

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=20080422230238.48c50ea0.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rdunlap@xenotime.net \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=torvalds@linux-foundation.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