From: Roland Dreier <roland@digitalvampire.org>
To: "chas williams - CONTRACTOR" <chas@cmf.nrl.navy.mil>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH 1/3][ATM]: [he] he_init_one() is declared __devinit, but calls __init functions
Date: Sun, 17 Sep 2006 14:54:47 -0700 [thread overview]
Message-ID: <87y7si40rc.fsf@digitalvampire.org> (raw)
In-Reply-To: <200609170018.k8H0IPxV025280@cmf.nrl.navy.mil> (chas williams's message of "Sat, 16 Sep 2006 20:18:25 -0400")
> author chas williams - CONTRACTOR <chas@thirdoffive.cmf.nrl.navy.mil> Sat, 16 Sep 2006 15:44:55 -0400
Not really a big deal -- but in general it's probably better to try
and preserve authorship information.
All you need is to add a
From: Roland Dreier <roland@digitalvampire.org>
line at the beginning of the body of the patch.
Thanks,
Roland
prev parent reply other threads:[~2006-09-17 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 0:18 [PATCH 1/3][ATM]: [he] he_init_one() is declared __devinit, but calls __init functions chas williams - CONTRACTOR
2006-09-17 21:54 ` Roland Dreier [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=87y7si40rc.fsf@digitalvampire.org \
--to=roland@digitalvampire.org \
--cc=chas@cmf.nrl.navy.mil \
--cc=davem@davemloft.net \
--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).