From: Jeff Garzik <jeff@garzik.org>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: csnook@redhat.com, bunk@stusta.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, atl1-devel@lists.sourceforge.net
Subject: Re: [PATCH netdev#atl1 1/1] atl1: clean up extern, global scope declarations
Date: Wed, 07 Feb 2007 17:14:18 -0500 [thread overview]
Message-ID: <45CA4F3A.5080000@garzik.org> (raw)
In-Reply-To: <20070207023453.GA2657@osprey.hogchain.net>
Jay Cliburn wrote:
> From: Jay Cliburn <jacliburn@bellsouth.net>
>
> atl1: move extern to header file; make some global code static
>
> Move an extern declaration to a header file. Make needlessly global
> functions static. Noticed by Adrian Bunk.
>
> Signed-off-by: Jay Cliburn <jacliburn@bellsouth.net>
applied
prev parent reply other threads:[~2007-02-07 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 2:34 [PATCH netdev#atl1 1/1] atl1: clean up extern, global scope declarations Jay Cliburn
2007-02-07 22:14 ` Jeff Garzik [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=45CA4F3A.5080000@garzik.org \
--to=jeff@garzik.org \
--cc=atl1-devel@lists.sourceforge.net \
--cc=bunk@stusta.de \
--cc=csnook@redhat.com \
--cc=jacliburn@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).