public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andi Kleen <ak@suse.de>
Cc: Gerd Knorr <kraxel@suse.de>, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] -mm5 has no i2c on amd64
Date: Tue, 20 Jan 2004 16:30:52 -0800	[thread overview]
Message-ID: <20040121003052.GB5472@kroah.com> (raw)
In-Reply-To: <20040120195132.1dbaabb8.ak@suse.de>

On Tue, Jan 20, 2004 at 07:51:32PM +0100, Andi Kleen wrote:
> On Tue, 20 Jan 2004 19:32:59 +0100
> Gerd Knorr <kraxel@suse.de> wrote:
> 
> > On Tue, Jan 20, 2004 at 01:59:46PM +0100, Andi Kleen wrote:
> > > Gerd Knorr <kraxel@bytesex.org> writes:
> > > > 
> > > > +++ linux-mm5-2.6.1/arch/x86_64/Kconfig	2004-01-20 13:15:10.000000000 +0100
> > > > +source "drivers/i2c/Kconfig"
> > > > +
> > > 
> > > There is no such source in arch/i386/Kconfig.  So it's probably wrong.
> > 
> > i386 includes that indirectly via drivers/Kconfig
> > So should the other archs do that too?
> 
> Yep. Or at least x86-64 should likely.
> 
> But it must have worked until recently because I got a report about I2C on x86-64 for 2.6.0.

Yes, I just moved the i2c Kconfig out of the char menu, and into the
main drivers/Kconfig.

And here I thought all of the archs had switched to using that file,
instead of trying to put together their own drivers menus :)

thanks,

greg k-h

  reply	other threads:[~2004-01-21  0:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040120124626.GA20023@bytesex.org.suse.lists.linux.kernel>
2004-01-20 12:59 ` [patch] -mm5 has no i2c on amd64 Andi Kleen
2004-01-20 18:19   ` Andrew Morton
2004-01-20 18:32   ` Gerd Knorr
2004-01-20 18:51     ` Andi Kleen
2004-01-21  0:30       ` Greg KH [this message]
2004-01-20 12:46 Gerd Knorr
2004-01-20 17:10 ` Andrew Morton
2004-01-20 18:11   ` Sam Ravnborg
2004-01-20 18:18 ` Andrew Morton

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=20040121003052.GB5472@kroah.com \
    --to=greg@kroah.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=kraxel@suse.de \
    --cc=linux-kernel@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