From: Erik Hugne <erik.hugne@ericsson.com>
To: Ying Xue <ying.xue@windriver.com>
Cc: <netdev@vger.kernel.org>, <tipc-discussion@lists.sourceforge.net>,
<jon.maloy@ericsson.com>, <richard.alpe@ericsson.com>,
<laszlo.benedek@ericsson.com>
Subject: Re: [PATCH net-next] tipc: sparse: fix htons conversion warnings
Date: Mon, 9 Mar 2015 10:44:22 +0100 [thread overview]
Message-ID: <20150309094422.GF9105@haze> (raw)
In-Reply-To: <54FD686F.9050604@windriver.com>
On Mon, Mar 09, 2015 at 05:31:27PM +0800, Ying Xue wrote:
> It's better to add original sparse warning messages in commit header.
The general practice under /net seems to be the opposite though.
I'll do a resend if necessary
//E
next prev parent reply other threads:[~2015-03-09 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 9:19 [PATCH net-next] tipc: sparse: fix htons conversion warnings erik.hugne
2015-03-09 9:31 ` Ying Xue
2015-03-09 9:44 ` Erik Hugne [this message]
2015-03-09 19:39 ` David Miller
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=20150309094422.GF9105@haze \
--to=erik.hugne@ericsson.com \
--cc=jon.maloy@ericsson.com \
--cc=laszlo.benedek@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=richard.alpe@ericsson.com \
--cc=tipc-discussion@lists.sourceforge.net \
--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).