All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: tklein@de.ibm.com, themann@de.ibm.com,
	Hannes Hering <hannes.hering@linux.vnet.ibm.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	ossrosch@linux.vnet.ibm.com, linuxppc-dev@ozlabs.org,
	raisch@de.ibm.com, Nathan Lynch <ntl@pobox.com>,
	ossthema@de.ibm.com
Subject: Re: [PATCH 2/3] [2.6.26] ehea: Add dependency to Kconfig
Date: Tue, 03 Jun 2008 17:11:30 -0400	[thread overview]
Message-ID: <4845B382.20205@garzik.org> (raw)
In-Reply-To: <1212527335.23656.2.camel@badari-desktop>

Badari Pulavarty wrote:
>> It would be nice to get this resolved for 2.6.26 -- this new
>> dependency causes working 2.6.25 configs to effectively fail (by
>> deselecting CONFIG_EHEA during make oldconfig).


When everybody else is happy, I'm happy :)

WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jeff@garzik.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Nathan Lynch <ntl@pobox.com>,
	Hannes Hering <hannes.hering@linux.vnet.ibm.com>,
	tklein@de.ibm.com, themann@de.ibm.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, raisch@de.ibm.com,
	ossrosch@linux.vnet.ibm.com, linuxppc-dev@ozlabs.org,
	ossthema@de.ibm.com
Subject: Re: [PATCH 2/3] [2.6.26] ehea: Add dependency to Kconfig
Date: Tue, 03 Jun 2008 17:11:30 -0400	[thread overview]
Message-ID: <4845B382.20205@garzik.org> (raw)
In-Reply-To: <1212527335.23656.2.camel@badari-desktop>

Badari Pulavarty wrote:
>> It would be nice to get this resolved for 2.6.26 -- this new
>> dependency causes working 2.6.25 configs to effectively fail (by
>> deselecting CONFIG_EHEA during make oldconfig).


When everybody else is happy, I'm happy :)


  reply	other threads:[~2008-06-03 21:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 12:43 [PATCH 2/3] [2.6.26] ehea: Add dependency to Kconfig Hannes Hering
2008-05-07 12:43 ` Hannes Hering
2008-05-28 16:44 ` Nathan Lynch
2008-05-28 16:44   ` Nathan Lynch
2008-06-03  8:07   ` Hannes Hering
2008-06-03  8:07     ` Hannes Hering
2008-06-03 20:49     ` Nathan Lynch
2008-06-03 20:49       ` Nathan Lynch
2008-06-03 21:08       ` Badari Pulavarty
2008-06-03 21:08         ` Badari Pulavarty
2008-06-03 21:11         ` Jeff Garzik [this message]
2008-06-03 21:11           ` Jeff Garzik
2008-06-03 22:30           ` [PATCH 1/2] make walk_memory_resource available with MEMORY_HOTPLUG=n Nathan Lynch
2008-06-03 22:30             ` Nathan Lynch
2008-06-06 19:43             ` Badari Pulavarty
2008-06-06 19:43               ` Badari Pulavarty
2008-06-06 23:06             ` Nathan Lynch
2008-06-07  5:48               ` Paul Mackerras
2008-06-03 22:31           ` [PATCH 2/2] ehea: remove dependency on MEMORY_HOTPLUG Nathan Lynch
2008-06-03 22:31             ` Nathan Lynch
2008-06-03 22:42             ` Jeff Garzik
2008-06-03 22:42               ` Jeff Garzik
2008-06-04  5:27               ` Yasunori Goto
2008-06-04  5:27                 ` Yasunori Goto

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=4845B382.20205@garzik.org \
    --to=jeff@garzik.org \
    --cc=hannes.hering@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=ntl@pobox.com \
    --cc=ossrosch@linux.vnet.ibm.com \
    --cc=ossthema@de.ibm.com \
    --cc=pbadari@us.ibm.com \
    --cc=raisch@de.ibm.com \
    --cc=themann@de.ibm.com \
    --cc=tklein@de.ibm.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.