From: Adrian Bunk <bunk@stusta.de>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: Andrew Morton <akpm@osdl.org>,
Xiong Huang <xiong_huang@attansic.com>,
Chris Snook <csnook@redhat.com>,
jgarzik@pobox.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [RFC: -mm patch] drivers/net/atl1/: possible cleanups
Date: Wed, 7 Feb 2007 01:24:05 +0100 [thread overview]
Message-ID: <20070207002405.GA12958@stusta.de> (raw)
In-Reply-To: <20070206181910.4d27046a@osprey.hogchain.net>
On Tue, Feb 06, 2007 at 06:19:10PM -0600, Jay Cliburn wrote:
> On Tue, 6 Feb 2007 23:12:29 +0100
> Adrian Bunk <bunk@stusta.de> wrote:
>...
> > This patch contains the following possible cleanups:
> > - move extern declarations to atl1.h
> > - make needlessly global code static
>
> Adrian,
>
> The atl1 driver currently follows this development pathway:
>
> developer -> netdev#atl1 -> netdev#ALL -> -mm
>
> Your patch is just a little bit out ahead of us. Some of your suggested
> changes are already in the pipeline; we're just waiting for Jeff to
> merge netdev#atl1 into netdev#ALL. Should be soon.
>
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> > ---
> >
> > BTW: Can we get a MAINTAINERS entry for this driver?
>
> Already submitted to netdev#atl1.
>
> http://lkml.org/lkml/2007/2/3/174
:-)
> > -s32 atl1_setup_ring_resources(struct atl1_adapter *adapter);
> > -void atl1_free_ring_resources(struct atl1_adapter *adapter);
> > +
> > +extern char atl1_driver_name[];
> > +extern char atl1_driver_version[];
>
> netdev#atl1 already has this change.
>
> The rest of these I'll bundle up and submit to netdev#atl1, too. Will
> that work for you?
>...
Do what you consider the right thing - I don't care how it gets into the
various trees.
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
prev parent reply other threads:[~2007-02-07 0:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070129204528.eb8d695e.akpm@osdl.org>
[not found] ` <20070131215241.GB2890@inferi.kami.home>
[not found] ` <20070131232130.GC4137@inferi.kami.home>
[not found] ` <1170358572.29240.292.camel@localhost.localdomain>
[not found] ` <1170360101.29240.297.camel@localhost.localdomain>
[not found] ` <20070201211137.GA2830@inferi.kami.home>
[not found] ` <1170369202.29240.339.camel@localhost.localdomain>
2007-02-02 19:18 ` dynticks + iptables almost stops the boot process [was: Re: 2.6.20-rc6-mm3] Mattia Dongili
2007-02-02 20:27 ` Thomas Gleixner
2007-02-02 20:43 ` Mattia Dongili
2007-02-06 16:48 ` Ingo Molnar
2007-02-06 19:28 ` Mattia Dongili
2007-02-06 23:12 ` Tilman Schmidt
2007-02-06 23:17 ` Thomas Gleixner
2007-02-07 1:01 ` Andrew Morton
2007-02-07 19:33 ` Ingo Molnar
2007-02-06 22:12 ` [RFC: -mm patch] drivers/net/atl1/: possible cleanups Adrian Bunk
2007-02-07 0:19 ` Jay Cliburn
2007-02-07 0:22 ` Jeff Garzik
2007-02-07 0:24 ` J. K. Cliburn
2007-02-07 0:24 ` Adrian Bunk [this message]
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=20070207002405.GA12958@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=csnook@redhat.com \
--cc=jacliburn@bellsouth.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiong_huang@attansic.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;
as well as URLs for NNTP newsgroup(s).