public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Jes Sorensen <jes@sgi.com>
Cc: Dave Jones <davej@redhat.com>,
	pfg@sgi.com, Linux Kernel <linux-kernel@vger.kernel.org>,
	tony.luck@intel.com, linux-ia64@vger.kernel.org
Subject: Re: [2.6 patch] drivers/sn/ must be entered for CONFIG_SGI_IOC3
Date: Thu, 19 Jan 2006 17:09:44 +0100	[thread overview]
Message-ID: <20060119160944.GN19398@stusta.de> (raw)
In-Reply-To: <yq0vewg7dc7.fsf@jaguar.mkp.net>

On Thu, Jan 19, 2006 at 04:54:00AM -0500, Jes Sorensen wrote:
> >>>>> "Adrian" == Adrian Bunk <bunk@stusta.de> writes:
> 
> Adrian> On Tue, Jan 17, 2006 at 06:55:21PM -0500, Dave Jones wrote:
> >> kernel/drivers/serial/ioc3_serial.ko needs unknown symbol
> >> ioc3_unregister_submodule
> >> 
> >> CONFIG_SERIAL_SGI_IOC3=m CONFIG_SGI_IOC3=m
> 
> Adrian> The untested patch below should fix it.
> 
> Actually I think this is more appropriate so we don't end up with 17
> cases that add drivers/sn to the build lib.
>...

I haven't tested your patch, but I agree that it's a better approach 
than my patch.
 
> Cheers,
> Jes
>...

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


  reply	other threads:[~2006-01-19 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 23:55 2.6.16rc1 ia64 missing symbol Dave Jones
2006-01-18 11:02 ` Jes Sorensen
2006-01-19  0:21   ` Dave Jones
2006-01-19  3:24 ` [2.6 patch] drivers/sn/ must be entered for CONFIG_SGI_IOC3 Adrian Bunk
2006-01-19  9:54   ` Jes Sorensen
2006-01-19 16:09     ` Adrian Bunk [this message]
2006-01-20  2:29     ` Dave Jones

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=20060119160944.GN19398@stusta.de \
    --to=bunk@stusta.de \
    --cc=davej@redhat.com \
    --cc=jes@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pfg@sgi.com \
    --cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox