public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Fengguang Wu <wfg-VuQAYsv1563Yd54FQh9/CA@public•gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public•gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
	containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public•gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public•gmane.org
Subject: Re: [PATCH] inet: Initialize per-netns inetpeer roots in net/ipv{4,6}/route.c
Date: Sun, 10 Jun 2012 14:47:48 +0800	[thread overview]
Message-ID: <20120610064748.GA10905@localhost> (raw)
In-Reply-To: <20120609.220421.2043389435765629622.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>

On Sat, Jun 09, 2012 at 10:04:21PM -0700, David Miller wrote:
> From: Fengguang Wu <wfg-VuQAYsv1563Yd54FQh9/CA@public•gmane.org>
> Date: Sun, 10 Jun 2012 12:49:34 +0800
> 
> > On Sun, Jun 10, 2012 at 12:43:39PM +0800, Fengguang Wu wrote:
> >> On Sat, Jun 09, 2012 at 09:21:47PM -0700, David Miller wrote:
> >> > From: Fengguang Wu <wfg-VuQAYsv1563Yd54FQh9/CA@public•gmane.org>
> >> > 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.
> > 
> > Or better, simply include a 
> > 
> >         Reported-by: Fengguang Wu <wfg-VuQAYsv1563Yd54FQh9/CA@public•gmane.org>
> 
> Now that on the other hand I should have done and was an oversight.

That's fine.

Please feel free to add that "Reported-by" to get verbose build report,
as well as to _NOT_ add the above line to avoid receiving reports when
the fix is obviously correct.

Ie. use the tag as a way to control my script.

> But all the other crap, is absolutely unreasonable of you to ask of me.

Yup.. Thanks for your time!

Regards,
Fengguang

  parent reply	other threads:[~2012-06-10  6:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-09 23:32 [PATCH] inet: Initialize per-netns inetpeer roots in net/ipv{4,6}/route.c David Miller
2012-06-10  1:58 ` Fengguang Wu
2012-06-10  2:04   ` David Miller
     [not found]     ` <20120609.190451.182034193302304295.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-06-10  3:16       ` Fengguang Wu
2012-06-10  4:21         ` David Miller
     [not found]           ` <20120609.212147.1738198233131370927.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-06-10  4:43             ` Fengguang Wu
2012-06-10  4:49               ` Fengguang Wu
2012-06-10  5:04                 ` David Miller
     [not found]                   ` <20120609.220421.2043389435765629622.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-06-10  6:47                     ` Fengguang Wu [this message]
2012-06-10  5:03               ` David Miller
2012-06-10  2:08   ` Fengguang Wu
2012-06-10  2:09     ` David Miller
     [not found]       ` <20120609.190929.1165462964087672866.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-06-10  2:18         ` David Miller
     [not found]           ` <20120609.221801.2226110181753212240.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-06-10  2:37             ` Fengguang Wu
2012-06-10 10:16             ` Fengguang Wu
2012-06-11  0:27               ` [PATCH] inet: Initialize per-netns inetpeer roots in net/ipv{4, 6}/route.c Gao feng
     [not found]                 ` <4FD53B74.1050409-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2012-06-11  1:44                   ` [PATCH] inet: Initialize per-netns inetpeer roots in net/ipv{4,6}/route.c Fengguang Wu
2012-06-11  3:03               ` David Miller
2012-06-10  5:14         ` [PATCH] inet: Initialize per-netns inetpeer roots in net/ipv{4, 6}/route.c Gao feng

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=20120610064748.GA10905@localhost \
    --to=wfg-vuqaysv1563yd54fqh9/ca@public$(echo .)gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public$(echo .)gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public$(echo .)gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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