All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@openedhand.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ian <spyro@f2s.com>,
	linux-next@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: mfd tree build failure
Date: Tue, 5 Aug 2008 18:08:42 +0200	[thread overview]
Message-ID: <20080805160840.GC6335@caravaggio> (raw)
In-Reply-To: <20080806020540.c22b1fa0.sfr@canb.auug.org.au>

On Wed, Aug 06, 2008 at 02:05:40AM +1000, Stephen Rothwell wrote:
> Hi Ian,
> 
> On Tue, 05 Aug 2008 16:39:54 +0100 ian <spyro@f2s.com> wrote:
> >
> > I'd have expected the other TMIO drivers to fail too.
> > 
> > get_irq_data is defined in linux/irq.h only if 
> > 
> > CONFIG_GENERIC_HARDIRQs is set and you arent on S390 (so why doesnt S390
> > fail?)
> > 
> > I dont see this as a big problem. As far as Im concerned, all the TMIO
> > drivers can depend on CONFIG_ARM.
> > 
> > It may not be a bad idea to add CONFIG_MFD_TMIO_SUBDEVICE so that TMIO
> > sub device drivers can only be selected when TMIO cores are selected.
> > This would neatly fix the earlier problem, rather than making al lthe
> > subdevices CONFIG_ARM.
> 
> It'd be real nice if someone did a patch to that effect :-)
:-) I'll take care of it, yep.

Cheers,
Samuel.

  reply	other threads:[~2008-08-05 16:08 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 14:08 linux-next: mfd tree build failure 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2010-01-19  4:06 Stephen Rothwell
2010-01-19 10:59 ` Samuel Ortiz
2010-01-19 11:34   ` Stephen Rothwell
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
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
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-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-10-06  2:02 Stephen Rothwell
2009-10-06  2:35 ` Haojian Zhuang
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-08  5:59         ` Haojian Zhuang
2009-10-12  2:11 ` 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
2008-08-05  5:09 Stephen Rothwell
2008-08-05 13:03 ` ian
2008-08-05 13:09   ` Samuel Ortiz
2008-08-05 13:22     ` Stephen Rothwell
2008-08-05 15:29     ` ian

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=20080805160840.GC6335@caravaggio \
    --to=sameo@openedhand.com \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.