From: David Miller <davem@davemloft.net>
To: ying.xue@windriver.com
Cc: steffen.klassert@secunet.com, dborkman@redhat.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: xfrm6: silence sparse warning
Date: Wed, 08 Jan 2014 00:56:56 -0500 (EST) [thread overview]
Message-ID: <20140108.005656.1582987448512057112.davem@davemloft.net> (raw)
In-Reply-To: <52CCE83D.5080909@windriver.com>
From: Ying Xue <ying.xue@windriver.com>
Date: Wed, 8 Jan 2014 13:55:09 +0800
> 3. Just drop the patch
This is the only suitable thing to do.
next prev parent reply other threads:[~2014-01-08 5:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 2:56 [PATCH net-next] net: xfrm6: silence sparse warning Ying Xue
2014-01-08 3:43 ` David Miller
2014-01-08 5:55 ` Ying Xue
2014-01-08 5:56 ` David Miller [this message]
2014-01-09 23:04 ` Stephen Hemminger
2014-01-10 2:53 ` Ben Hutchings
2014-01-10 5:30 ` Stephen Hemminger
2014-01-08 20:46 ` Ben Hutchings
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=20140108.005656.1582987448512057112.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=ying.xue@windriver.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).