Linux s390 Architecture development
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: linux-s390@vger.kernel.org
Subject: Re: Build failure after "phylib: remove !S390 dependeny from Kconfig"
Date: Mon, 06 May 2013 14:47:29 +0000	[thread overview]
Message-ID: <1367851649.4569.119.camel@chaos.site> (raw)
In-Reply-To: <20130506131040.GC4322@osiris>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]

Le Monday 06 May 2013 � 15:10 +0200, Heiko Carstens a �crit :
> On Mon, May 06, 2013 at 01:40:07PM +0200, Jean Delvare wrote:
> > > (...)
> > > Well, I'm fine with your patch. As long as we don't have a nice solution
> > > for s390 being the only architecture with !GENERIC_HARDIRQS we will have
> > > to live with Kconfig hacks. Unfortunately.
> > 
> > OK. Will you pick what I sent as is, or do you want me to resend it
> > somewhere? Just let me know. FWIW I think this should go to the 3.9
> > stable kernel branch.
> 
> Since the patch is bit odd I think it should go to David Miller.

Not sure if David would enjoy reading that ;)

OK, I'll send it to David.

-- 
Jean Delvare
Suse L3

           reply	other threads:[~2013-05-06 14:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20130506131040.GC4322@osiris>]

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=1367851649.4569.119.camel@chaos.site \
    --to=jdelvare@suse.de \
    --cc=linux-s390@vger.kernel.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