[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120610044339.GA10436@localhost>
Date: Sun, 10 Jun 2012 12:43:39 +0800
From: Fengguang Wu <wfg@...ux.intel.com>
To: David Miller <davem@...emloft.net>
Cc: netdev@...r.kernel.org, gaofeng@...fujitsu.com,
containers@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] inet: Initialize per-netns inetpeer roots in
net/ipv{4,6}/route.c
On Sat, Jun 09, 2012 at 09:21:47PM -0700, David Miller wrote:
> From: Fengguang Wu <wfg@...ux.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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists