From: David Miller <davem@davemloft.net>
To: xemul@parallels.com
Cc: shanwei88@gmail.com, netdev@vger.kernel.org, davidshan@tencent.com
Subject: Re: [PATCH net-next] net: sock_diag_handler structs can be const
Date: Wed, 25 Apr 2012 20:47:39 -0400 (EDT) [thread overview]
Message-ID: <20120425.204739.357701276066555791.davem@davemloft.net> (raw)
In-Reply-To: <4F97EE11.2090408@parallels.com>
From: Pavel Emelyanov <xemul@parallels.com>
Date: Wed, 25 Apr 2012 16:29:05 +0400
> On 04/25/2012 08:21 AM, Shan Wei wrote:
>> From: Shan Wei <davidshan@tencent.com>
>>
>> read only, so change it to const.
>>
>> Signed-off-by: Shan Wei <davidshan@tencent.com>
>
> Acked-by: Pavel Emelyanov <xemul@parallels.com>
Applied.
prev parent reply other threads:[~2012-04-26 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 4:21 [PATCH net-next] net: sock_diag_handler structs can be const Shan Wei
2012-04-25 12:29 ` Pavel Emelyanov
2012-04-26 0:47 ` 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=20120425.204739.357701276066555791.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davidshan@tencent.com \
--cc=netdev@vger.kernel.org \
--cc=shanwei88@gmail.com \
--cc=xemul@parallels.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).