From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, jeff@garzik.org, bruce.w.allan@intel.com
Subject: Re: [NET-2.6 PATCH] e100: cosmetic cleanup
Date: Sun, 04 Jan 2009 17:13:45 -0800 (PST) [thread overview]
Message-ID: <20090104.171345.257011394.davem@davemloft.net> (raw)
In-Reply-To: <20081231233057.23132.43080.stgit@lost.foo-projects.org>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Wed, 31 Dec 2008 15:31:50 -0800
> Add missing space after if, switch, for and while keywords.
>
> Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
I find it kind of rotten that you held up the e100 firmware
submission so you could do "important testing" and then
you fire off a completely useless patch like this meanwhile.
Applied, but know that this kind of prioritization really
and truly ticks me off.
next prev parent reply other threads:[~2009-01-05 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 23:31 [NET-2.6 PATCH] e100: cosmetic cleanup Jeff Kirsher
2009-01-05 1:13 ` David Miller [this message]
2009-01-05 2:28 ` Jeff Kirsher
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=20090104.171345.257011394.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bruce.w.allan@intel.com \
--cc=jeff@garzik.org \
--cc=jeffrey.t.kirsher@intel.com \
--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).