linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Chris Snook <csnook@redhat.com>
Cc: info@netxen.com, Patrick McHardy <kaber@coreworks.de>,
	Judy Fischbach <jfisch@cs.pdx.edu>,
	Luke Yang <luke.yang@analog.com>,
	bonding-devel@lists.sourceforge.net,
	Bryan Wu <bryan.wu@analog.com>,
	kong.lai@tundra.com, Jay Vosburgh <fubar@us.ibm.com>,
	James Morris <jmorris@namei.org>,
	linuxppc-embedded@ozlabs.org,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	Alex V Lasso <a_villacis@palosanto.com>,
	Ulrich Kunitz <kune@deine-taler.de>,
	Chad Tindel <ctindel@users.sourceforge.net>,
	Amit S Kale <amitkale@netxen.com>,
	Jay Cliburn <jcliburn@gmail.com>,
	Samuel Ortiz <samuel@sortiz.org>, Brian Pugh <bpugh@cs.pdx.edu>,
	Daniel Drake <dsd@gentoo.org>,
	alexandre.bounine@tundra.com,
	Pantelis Antoniou <panto@intracom.gr>,
	netdev@vger.kernel.org, Jesper Juhl <jesper.juhl@gmail.com>,
	linux-wireless@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	Vitaly Bordug <vbordug@ru.mvista.com>,
	Lukasz Stelmach <stlman@poczta.fm>,
	Ron Mercer <linux-driver@qlogic.com>,
	atl1-devel@lists.sourceforge.net,
	Andrew Morton <akpm@linux-foundation.org>,
	"David S. Miller" <davem@davemloft.net>,
	James P Ketrenos <ipw2100-admin@linux.intel.com>
Subject: Re: [PATCH][12/37] Clean up duplicate includes in drivers/net/
Date: Sat, 21 Jul 2007 17:46:21 +0100	[thread overview]
Message-ID: <20070721164621.GN21668@ftp.linux.org.uk> (raw)
In-Reply-To: <46A236FC.2080300@redhat.com>

On Sat, Jul 21, 2007 at 12:40:28PM -0400, Chris Snook wrote:
> Define "duplicate".  I ask because this patch just got posted a few days 
> ago:

... and it had been wrong - it's really a duplicate (check several lines
above).  My apologies.

  reply	other threads:[~2007-07-21 16:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21 15:02 [PATCH][12/37] Clean up duplicate includes in drivers/net/ Jesper Juhl
2007-07-21 16:40 ` Chris Snook
2007-07-21 16:46   ` Al Viro [this message]
2007-07-21 16:48   ` Jesper Juhl
2007-07-21 16:50     ` Chris Snook
2007-07-23 13:22 ` 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=20070721164621.GN21668@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=a_villacis@palosanto.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexandre.bounine@tundra.com \
    --cc=amitkale@netxen.com \
    --cc=atl1-devel@lists.sourceforge.net \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=bpugh@cs.pdx.edu \
    --cc=bryan.wu@analog.com \
    --cc=csnook@redhat.com \
    --cc=ctindel@users.sourceforge.net \
    --cc=davem@davemloft.net \
    --cc=dsd@gentoo.org \
    --cc=fubar@us.ibm.com \
    --cc=info@netxen.com \
    --cc=ipw2100-admin@linux.intel.com \
    --cc=jcliburn@gmail.com \
    --cc=jesper.juhl@gmail.com \
    --cc=jfisch@cs.pdx.edu \
    --cc=jmorris@namei.org \
    --cc=kaber@coreworks.de \
    --cc=kong.lai@tundra.com \
    --cc=kune@deine-taler.de \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-driver@qlogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=luke.yang@analog.com \
    --cc=netdev@vger.kernel.org \
    --cc=panto@intracom.gr \
    --cc=ralf@linux-mips.org \
    --cc=samuel@sortiz.org \
    --cc=stlman@poczta.fm \
    --cc=vbordug@ru.mvista.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).