From: Denys Vlasenko <dvlasenk@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Deinline __nlmsg_put and genlmsg_put. -7k code on i386 defconfig
Date: Mon, 30 Jan 2012 20:37:00 +0100 [thread overview]
Message-ID: <4F26F15C.9080808@redhat.com> (raw)
In-Reply-To: <20120130.131104.1782962680660646529.davem@davemloft.net>
On 01/30/2012 07:11 PM, David Miller wrote:
> This doesn't apply to net-next, it appears it was corrupted by your
> email client:
>
>> -static __inline__ struct nlmsghdr *
>> -__nlmsg_put(struct sk_buff *skb, u32 pid, u32 seq, int type, int len,
>> -int flags)
>
> It appears to have chopped up a long line here, for example.
I rediffed the patch against net-next, compile-tested it and going
to send it using git-send-email in a minute.
--
vda
prev parent reply other threads:[~2012-01-30 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 19:02 [PATCH] Deinline __nlmsg_put and genlmsg_put. -7k code on i386 defconfig Denys Vlasenko
2012-01-30 18:11 ` David Miller
2012-01-30 19:37 ` Denys Vlasenko [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=4F26F15C.9080808@redhat.com \
--to=dvlasenk@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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).