From: "Michael Marineau" <mike@marineau.org>
To: "David Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] fix for initial link state in 2.6.28
Date: Sun, 4 Jan 2009 21:11:10 -0500 [thread overview]
Message-ID: <c0526ddf0901041811v11015db7oa080f5b1dfd3db6f@mail.gmail.com> (raw)
In-Reply-To: <20090104.171839.14814429.davem@davemloft.net>
On Sun, Jan 4, 2009 at 8:18 PM, David Miller <davem@davemloft.net> wrote:
>
> I find it mysterious how someone can write such an excellent
> patch and such a well written commit message, then in the
> end not give a proper signoff for their changes :-/
Being completely unfamiliar with network drivers I was a bit fried
after tracing though enough code to finally understand what was going
on so it slipped my mind. :-)
>
> Applied, and queued up for -stable, but please provide proper
> signoffs in the future.
Noted. Thanks for queuing it up!
--
Michael Marineau
mike@marineau.org
prev parent reply other threads:[~2009-01-05 2:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 23:12 [PATCH] fix for initial link state in 2.6.28 Michael Marineau
2009-01-05 1:18 ` David Miller
2009-01-05 2:11 ` Michael Marineau [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=c0526ddf0901041811v11015db7oa080f5b1dfd3db6f@mail.gmail.com \
--to=mike@marineau.org \
--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).