From: Randy Dunlap <RANDY.DUNLAP@ORACLE.COM>
To: "Randy.Dunlap" <rdunlap@xenotime.net>,
Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Harvey Harrison <harvey.harrison@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mfd: kconfig exposing unbuildable driver
Date: Tue, 22 Apr 2008 16:06:14 -0500 (CDT) [thread overview]
Message-ID: <8411091.1208898374115.JavaMail.oracle@acsmt302.oracle.com> (raw)
In-Reply-To: <20080422210153.GB21435@flint.arm.linux.org.uk>
--- Original Message --- (from rmk:)
> 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.
Sure.
> Meanwhile, pHilipp Zabel believes this hardware not to be ARM
> specific.
That's the big Important missing info. So the source file is
incorrect, not the Kconfig.l
> So, the majority concensus in the three way discussion was
> that it
> should remain visible, and the (unnecessary) include and its
> dependents be removed.
>
> Having now had some time (read: half an hour after dinner after
> getting
> back home) to investigate, I can point to the patch in several
> places:
>
> http://ftp.arm.linux.org.uk/pub/armlinux/kernel/git-cur/arm:devel.mbox
>
> and find the patch with subject line:
>
> [ARM] 5010/1: htc-pasic3: remove unused defines and includes
>
> or grab 5010/1 from my patch system. If you want a patch to
> plaster over it, merging that would be a far better solution.
OK, sounds fair. Thanks.
~Randy
next prev parent reply other threads:[~2008-04-22 21:06 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 [this message]
2008-04-23 6:02 ` Andrew Morton
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=8411091.1208898374115.JavaMail.oracle@acsmt302.oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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