From: David Miller <davem@davemloft.net>
To: pcnet32@verizon.net
Cc: netdev@vger.kernel.org
Subject: Re: patch acceptance question
Date: Thu, 09 Jul 2009 17:10:33 -0700 (PDT) [thread overview]
Message-ID: <20090709.171033.138040764.davem@davemloft.net> (raw)
In-Reply-To: <1247152896.29603.15.camel@localhost.localdomain>
From: Don Fry <pcnet32@verizon.net>
Date: Thu, 09 Jul 2009 08:21:36 -0700
> I was surprised today to see a change to pcnet32.c in 2.6.31-rc2-git4
> which maybe I missed yesterday on netdev. Most of the changes are okay,
> but one in particular will result in some ugly printing.
>
> What is the path that (probably janitorial) changes take that get
> included in mainline? Had I seen it before it went in I would have
> commented on it then.
In the amount of typing you did for sending this email, you
could have submitted a fix instead.
I think the change in question went straight into Linus's tree.
prev parent reply other threads:[~2009-07-10 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 15:21 patch acceptance question Don Fry
2009-07-10 0:10 ` 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=20090709.171033.138040764.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pcnet32@verizon.net \
/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