From: Samuel Ortiz <sameo@openedhand.com>
To: ian <spyro@f2s.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Subject: Re: linux-next: mfd tree build failure
Date: Tue, 5 Aug 2008 15:09:00 +0200 [thread overview]
Message-ID: <20080805130900.GB6335@caravaggio> (raw)
In-Reply-To: <1217941394.18866.19.camel@wirenth>
Hi Ian,
On Tue, Aug 05, 2008 at 02:03:14PM +0100, ian wrote:
> On Tue, 2008-08-05 at 15:09 +1000, Stephen Rothwell wrote:
> >
> > I reverted commit 4d6da2de1b09228989efb67a1f9e6d2ced075540 ("mfd:
> > driver for the TMIO NAND controller") until it has tighter controls in
> > its Kconfig patch. i.e. I have no idea what arches this should be
> > built on.
>
> Since there is no way to know wether an arch has readsw() and friends at
> config time, I'd propose that bot the TMIO NAND and MMC drivers be built
> only on ARM for now. If anyone every uses them on another platform, they
> can add the support.
>
> Should I redo the two drivers patchsets, or would you prefer a patch
> fixing this after the fact?
No worries, I'll fix the Kconfigs later today.
Cheers,
Samuel.
next prev parent reply other threads:[~2008-08-05 13:09 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 5:09 linux-next: mfd tree build failure Stephen Rothwell
2008-08-05 13:03 ` ian
2008-08-05 13:09 ` Samuel Ortiz [this message]
2008-08-05 13:22 ` Stephen Rothwell
2008-08-05 15:29 ` ian
-- strict thread matches above, loose matches on Subject: below --
2008-08-05 14:08 Stephen Rothwell
2008-08-05 15:39 ` ian
2008-08-05 16:05 ` Adrian Bunk
2008-08-05 18:50 ` ian
2008-08-05 16:05 ` Stephen Rothwell
2008-08-05 16:08 ` Samuel Ortiz
2008-08-05 16:16 ` Stephen Rothwell
2008-08-05 17:40 ` Samuel Ortiz
2008-08-05 18:46 ` ian
2008-08-06 9:53 ` Samuel Ortiz
2008-08-06 0:40 ` Stephen Rothwell
2009-01-12 3:03 Stephen Rothwell
2009-01-12 10:07 ` Balaji Rao
2009-01-13 6:24 ` Stephen Rothwell
2009-01-14 12:12 ` Samuel Ortiz
2009-10-06 2:02 Stephen Rothwell
2009-10-06 2:35 ` Haojian Zhuang
2009-10-06 3:54 ` Stephen Rothwell
2009-10-06 4:19 ` Haojian Zhuang
2009-10-08 5:59 ` Haojian Zhuang
2009-10-12 2:11 ` Stephen Rothwell
2009-11-23 3:35 Stephen Rothwell
2009-11-23 12:26 ` Samuel Ortiz
2009-11-23 16:32 ` Dmitry Torokhov
2009-11-24 23:35 ` Samuel Ortiz
2009-11-23 3:41 Stephen Rothwell
2009-11-23 4:03 ` Stephen Rothwell
2009-11-23 12:29 ` Samuel Ortiz
2009-11-23 13:11 ` Mark Brown
2009-11-23 14:44 ` Samuel Ortiz
2009-11-23 15:20 ` Mark Brown
2009-11-24 5:37 Stephen Rothwell
2009-11-24 9:57 ` Mark Brown
2009-11-24 10:14 ` Stephen Rothwell
2009-11-24 10:40 ` Mark Brown
2010-01-11 5:02 Stephen Rothwell
2010-01-11 10:51 ` Mark Brown
2010-01-11 12:02 ` Haojian Zhuang
2010-01-11 12:33 ` Samuel Ortiz
2010-01-11 22:44 ` Stephen Rothwell
2010-01-19 4:06 Stephen Rothwell
2010-01-19 10:59 ` Samuel Ortiz
2010-01-19 11:34 ` Stephen Rothwell
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=20080805130900.GB6335@caravaggio \
--to=sameo@openedhand.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=spyro@f2s.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