From: Adrian Bunk <bunk@kernel.org>
To: Brice Goglin <brice@myri.com>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
Jeff Garzik <jgarzik@redhat.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
linux-kernel@vger.kernel.org, apw@shadowen.org,
linuxppc-dev@ozlabs.org, sam@ravnborg.org,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
"Sosnowski, Maciej" <maciej.sosnowski@intel.com>
Subject: Re: [BUILD_FAILURE] 2.6.27-git2 - allyesconfig on powerpc selectsCONFIG_INTEL_IOATDMA=y
Date: Tue, 14 Oct 2008 12:35:41 +0300 [thread overview]
Message-ID: <20081014093541.GA10453@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <48F4627E.30300@myri.com>
On Tue, Oct 14, 2008 at 11:12:30AM +0200, Brice Goglin wrote:
> Adrian Bunk wrote:
> > But considering that igb is in a similar situation it would be nice if
> > all 3 drivers would handle it the same way.
> >
>
> Jesse,
> What do you think of the below patch?
> I am not very familiar with Kconfig, but it seems to solve the problem.
> If a Kconfig guru could double-check...
The patch looks good, but the main problem is to get an agreement
on the policy.
> Brice
>...
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-10-14 9:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 10:15 [BUILD_FAILURE] 2.6.27-git2 - allyesconfig on powerpc selects CONFIG_INTEL_IOATDMA=y Kamalesh Babulal
2008-10-13 11:26 ` Adrian Bunk
2008-10-13 12:02 ` Brice Goglin
2008-10-13 18:05 ` [BUILD_FAILURE] 2.6.27-git2 - allyesconfig on powerpc selectsCONFIG_INTEL_IOATDMA=y Brandeburg, Jesse
2008-10-13 18:21 ` Brice Goglin
2008-10-13 18:35 ` Adrian Bunk
2008-10-14 9:12 ` Brice Goglin
2008-10-14 9:35 ` Adrian Bunk [this message]
2008-10-14 16:10 ` Brandeburg, Jesse
2008-10-14 17:58 ` Adrian Bunk
2008-10-15 7:53 ` Kamalesh Babulal
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=20081014093541.GA10453@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=apw@shadowen.org \
--cc=brice@myri.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jgarzik@redhat.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=maciej.sosnowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®