From: David Miller <davem@davemloft.net>
To: panweiping3@gmail.com
Cc: fubar@us.ibm.com, andy@greyhouse.net,
lucas.demarchi@profusion.mobi, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] net: fix tranmitted/tranmitting typo
Date: Mon, 11 Apr 2011 13:17:45 -0700 (PDT) [thread overview]
Message-ID: <20110411.131745.102548357.davem@davemloft.net> (raw)
In-Reply-To: <1302516958-9535-1-git-send-email-panweiping3@gmail.com>
From: Weiping Pan(潘卫平) <panweiping3@gmail.com>
Date: Mon, 11 Apr 2011 18:15:57 +0800
> replace tranmitted with transmitted.
> replace tranmitting with transmitting.
>
> Signed-off-by: Weiping Pan(潘卫平) <panweiping3@gmail.com>
Applied.
prev parent reply other threads:[~2011-04-11 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 10:15 [PATCH 2/4] net: fix tranmitted/tranmitting typo Weiping Pan(潘卫平)
2011-04-11 20:17 ` 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=20110411.131745.102548357.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=netdev@vger.kernel.org \
--cc=panweiping3@gmail.com \
/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).