From: Fengguang Wu <wfg@linux.intel.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, gaofeng@cn.fujitsu.com,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] inet: Initialize per-netns inetpeer roots in net/ipv{4,6}/route.c
Date: Sun, 10 Jun 2012 12:43:39 +0800 [thread overview]
Message-ID: <20120610044339.GA10436@localhost> (raw)
In-Reply-To: <20120609.212147.1738198233131370927.davem@davemloft.net>
On Sat, Jun 09, 2012 at 09:21:47PM -0700, David Miller wrote:
> From: Fengguang Wu <wfg@linux.intel.com>
> Date: Sun, 10 Jun 2012 11:16:34 +0800
>
> > In long run, such build-fix patches can also be auto tested and
> > reported, somehow in this way. You just create a temporary branch
>
> Sorry, no.
That's fine. Then how about including some text "fix build errors" or
"fix build warnings" or paste the original gcc error/warning messages,
somewhere in the changelog or subject?
That will also allow me recognize that it's a build fix commit and to
make it unconditionally report back any build results.
Thanks,
Fengguang
next prev parent reply other threads:[~2012-06-10 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120609.163202.516027044484907548.davem@davemloft.net>
[not found] ` <20120610015832.GA9175@localhost>
[not found] ` <20120609.190451.182034193302304295.davem@davemloft.net>
2012-06-10 3:16 ` [PATCH] inet: Initialize per-netns inetpeer roots in net/ipv{4,6}/route.c Fengguang Wu
2012-06-10 4:21 ` David Miller
2012-06-10 4:43 ` Fengguang Wu [this message]
2012-06-10 4:49 ` Fengguang Wu
2012-06-10 5:04 ` David Miller
2012-06-10 6:47 ` Fengguang Wu
2012-06-10 5:03 ` 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=20120610044339.GA10436@localhost \
--to=wfg@linux.intel.com \
--cc=containers@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gaofeng@cn.fujitsu.com \
--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