From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: ron.mercer@qlogic.com, linux-driver@qlogic.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] drivers/net/qlge: Remove duplicated initial DUMP_ macro entries
Date: Wed, 21 Jul 2010 14:43:33 -0700 (PDT) [thread overview]
Message-ID: <20100721.144333.82796756.davem@davemloft.net> (raw)
In-Reply-To: <1279747141.1909.22.camel@Joe-Laptop.home>
From: Joe Perches <joe@perches.com>
Date: Wed, 21 Jul 2010 14:19:01 -0700
> There are a couple of errors in the previous patch.
> Two of the first DUMP_<foo> entries are duplicated.
> Sorry, bad use of emacs macros...
>
> Signed-off-by: Joe Perches <joe@perches.com>
Since I didn't push your original change out yet, I'll just add this
to the original commit.
Thanks!
prev parent reply other threads:[~2010-07-21 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 21:49 [PATCH net-next] drivers/net/qlge: Use pr_<level>, shrink text a bit Joe Perches
2010-07-21 20:58 ` David Miller
2010-07-21 21:19 ` [PATCH net-next] drivers/net/qlge: Remove duplicated initial DUMP_ macro entries Joe Perches
2010-07-21 21:43 ` David Miller [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=20100721.144333.82796756.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-driver@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ron.mercer@qlogic.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).