From: Wang Weidong <wangweidong1@huawei.com>
To: David Miller <davem@davemloft.net>
Cc: <jon.maloy@ericsson.com>, <allan.stephens@windriver.com>,
<erik.hugne@ericsson.com>, <maloy@donjonn.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH RESEND net-next 0/4] tipc: do some clean up
Date: Tue, 17 Dec 2013 09:18:01 +0800 [thread overview]
Message-ID: <52AFA649.30209@huawei.com> (raw)
In-Reply-To: <20131216.125810.539288997761338863.davem@davemloft.net>
On 2013/12/17 1:58, David Miller wrote:
> From: Wang Weidong <wangweidong1@huawei.com>
> Date: Mon, 16 Dec 2013 20:40:27 +0800
>
>> This patch series do some small clean up in tipc. And add reviewed-by
>> Erik and Jon.
>
> There is absolutely no reason for you to send this again, your
> original patches were queued up in patchwork and I was going to get to
> it shortly.
>
> In fact I applied them just now.
>
>
Ok. Sorry for resending these. Next time I should look up the patchwork
before resending patches.
Regards.
Wang
prev parent reply other threads:[~2013-12-17 1:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 12:40 [PATCH RESEND net-next 0/4] tipc: do some clean up Wang Weidong
2013-12-16 12:40 ` [PATCH net-next 1/4] tipc: remove unnecessary variables and conditions Wang Weidong
2013-12-16 13:33 ` David Laight
2013-12-16 14:16 ` Wang Weidong
2013-12-16 12:40 ` [PATCH net-next 2/4] tipc: kill unnecessary goto's Wang Weidong
2013-12-16 13:30 ` David Laight
2013-12-16 14:19 ` Wang Weidong
2013-12-16 18:01 ` David Miller
2013-12-17 6:00 ` Wang Weidong
2013-12-16 12:40 ` [PATCH net-next 3/4] tipc: Use <linux/uaccess.h> instead of <asm/uaccess.h> Wang Weidong
2013-12-16 12:40 ` [PATCH net-next 4/4] tipc: change lock_sock order in connect() Wang Weidong
2013-12-16 17:58 ` [PATCH RESEND net-next 0/4] tipc: do some clean up David Miller
2013-12-17 1:18 ` Wang Weidong [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=52AFA649.30209@huawei.com \
--to=wangweidong1@huawei.com \
--cc=allan.stephens@windriver.com \
--cc=davem@davemloft.net \
--cc=erik.hugne@ericsson.com \
--cc=jon.maloy@ericsson.com \
--cc=maloy@donjonn.com \
--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).