From: Jeff Garzik <jgarzik@pobox.com>
To: Daniele Venzano <webvenza@libero.it>
Cc: NetDev <netdev@oss.sgi.com>
Subject: Re: [PATCH 1/5] sis900 debugging and revision code
Date: Thu, 06 Jan 2005 18:35:48 -0500 [thread overview]
Message-ID: <41DDCB54.2080101@pobox.com> (raw)
In-Reply-To: <20041212123031.GB16325@gateway.milesteg.arr>
Patches 1, 2, and 5 are OK.
For the other two patches, I don't want to deviate from the style that
has been standard for years: dev->name prefix, followed by message.
It may make greps easier for you, but it becomes a non-standard style
and may make existing sysadmin scripts out in the field.
Please resend series without the PFX-where-devname-is-known changes.
Jeff
next prev parent reply other threads:[~2005-01-06 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-12 12:18 [PATCH 0/5] sis900 debugging and revision code Daniele Venzano
2004-12-12 12:30 ` [PATCH 1/5] " Daniele Venzano
2005-01-06 23:35 ` Jeff Garzik [this message]
2005-01-07 11:58 ` Daniele Venzano
2004-12-12 12:31 ` [PATCH 2/5] " Daniele Venzano
2004-12-12 12:32 ` [PATCH 3/5] " Daniele Venzano
2004-12-12 12:33 ` [PATCH 4/5] " Daniele Venzano
2004-12-12 12:34 ` [PATCH 5/5] " Daniele Venzano
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=41DDCB54.2080101@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=webvenza@libero.it \
/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).