linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Michael Buesch <mb@bu3sch.de>,
	John Linville <linville@tuxdriver.com>,
	Felix Fietkau <nbd@openwrt.org>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ssb: Make extif driver compilation depend on extif  config
Date: Wed, 8 Aug 2007 16:43:27 -0700	[thread overview]
Message-ID: <20070808164327.45803a64.akpm@linux-foundation.org> (raw)
In-Reply-To: <46BA4E24.3060400@aurel32.net>

On Thu, 09 Aug 2007 01:13:40 +0200
Aurelien Jarno <aurelien@aurel32.net> wrote:

> Andrew Morton a __crit :
> > mips allmodconfig:
> > 
> > drivers/ssb/driver_pcicore.c: In function `ssb_fixup_pcibridge':
> > drivers/ssb/driver_pcicore.c:98: error: implicit declaration of function `pcibios_enable_device'
> > drivers/ssb/driver_pcicore.c: At top level:
> > drivers/ssb/driver_pcicore.c:278: warning: integer overflow in expression
> > drivers/ssb/driver_pcicore.c:278: warning: integer overflow in expression
> 
> Those looks like real errors.

They seems to have gone away after I droped the duplicated patches.

> > drivers/ssb/driver_extif.c:125: error: redefinition of 'extif_read32'
> > drivers/ssb/driver_extif.c:21: error: previous definition of 'extif_read32' was here
> > drivers/ssb/driver_extif.c:130: error: redefinition of 'extif_write32'
> > drivers/ssb/driver_extif.c:26: error: previous definition of 'extif_write32' was here
> > drivers/ssb/driver_extif.c:136: error: redefinition of 'serial_exists'
> > drivers/ssb/driver_extif.c:32: error: previous definition of 'serial_exists' was here
> > drivers/ssb/driver_extif.c:150: error: redefinition of 'ssb_extif_serial_init'
> > drivers/ssb/driver_extif.c:46: error: previous definition of 'ssb_extif_serial_init' was here
> > drivers/ssb/driver_extif.c:181: error: redefinition of 'ssb_extif_timing_init'
> > drivers/ssb/driver_extif.c:77: error: previous definition of 'ssb_extif_timing_init' was here
> > drivers/ssb/driver_extif.c:203: error: redefinition of 'ssb_extif_get_clockcontrol'
> > drivers/ssb/driver_extif.c:99: error: previous definition of 'ssb_extif_get_clockcontrol' was here
> > 
> 
> All the versions of driver_extif.c I have seen have at maximum around
> 100 lines. It looks like a patch applied twice, which make the same code
> appearing twice in the .c file.

Yeah.  I dropped a bunch of things which seemed to help.

I'm hopelessly confused by the ssb stuff.  I'm not sure if I have all the
right stuff, all the latest stuff and I don't understand why some is going
into git-wireless and some is not.

I'd prefer to be dumbly pulling a tree which Michael controls rather than
trying to master it all in -mm, if possible.  A git tree or a quilt tree in
some open dir somewhere would suit?



  reply	other threads:[~2007-08-08 23:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 15:44 [PATCH] ssb: Make extif driver compilation depend on extif config Michael Buesch
2007-08-08 22:48 ` Andrew Morton
2007-08-08 23:13   ` Aurelien Jarno
2007-08-08 23:43     ` Andrew Morton [this message]
2007-08-08 23:58       ` Andrew Morton
2007-08-09  0:02       ` Michael Buesch
2007-08-09  0:10         ` Andrew Morton
2007-08-09  0:20           ` Michael Buesch
2007-08-09  0:28             ` Andrew Morton
2007-08-09  9:54               ` Michael Buesch
2007-08-09  9:44             ` Aurelien Jarno
2007-08-09  0:13         ` Andrew Morton
2007-08-09 14:01           ` John W. Linville
2007-08-09 14:38             ` Michael Buesch
2007-08-09 13:53       ` John W. Linville
2007-08-09 14:08         ` Michael Buesch
2007-08-09 14:23           ` John W. Linville

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=20070808164327.45803a64.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aurelien@aurel32.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=nbd@openwrt.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;
as well as URLs for NNTP newsgroup(s).