From: Philip Li <philip.li@intel.com>
To: David Miller <davem@davemloft.net>
Cc: lkp@intel.com, wang.yi59@zte.com.cn, wang.liang82@zte.com.cn,
yoshfuji@linux-ipv6.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, cheng.lin130@zte.com.cn,
kbuild-all@01.org, xue.zhihong@zte.com.cn, kuznet@ms2.inr.ac.ru
Subject: Re: [kbuild-all] [PATCH] ipv6: Not to probe neighbourless routes
Date: Fri, 30 Aug 2019 09:00:51 +0800 [thread overview]
Message-ID: <20190830010051.GB857@intel.com> (raw)
In-Reply-To: <20190829.163742.2109211377942652910.davem@davemloft.net>
On Thu, Aug 29, 2019 at 04:37:42PM -0700, David Miller wrote:
>
> So yeah, this is one instance where the kbuild test robot's report is
> making more rather than less work for us.
sorry for the inconvenience caused. We monitor the lkml, and as you
point out, we will continuously improve to provide faster response.
>
> We identified the build problem within hours of this patch being
> posted and the updated version was posted more than 24 hours ago.
>
> The kbuild robot should really have a way to either:
>
> 1) Report build problems faster, humans find the obvious cases like
> this one within a day or less.
thanks, we will continue working on this to speed up
>
> 2) Notice that a new version of the patch was posted or that a human
> responded to the patch pointing out the build problem.
thanks, we will enhance the patch testing to consider these ideas.
>
> Otherwise we get postings like this which is just more noise to
> delete.
>
> Thanks.
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
next prev parent reply other threads:[~2019-08-30 0:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 9:08 [PATCH] ipv6: Not to probe neighbourless routes Yi Wang
2019-08-27 15:22 ` Eric Dumazet
2019-08-27 20:49 ` David Miller
2019-08-29 22:20 ` kbuild test robot
2019-08-29 23:37 ` David Miller
2019-08-30 1:00 ` Philip Li [this message]
2019-08-29 22:42 ` kbuild test robot
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=20190830010051.GB857@intel.com \
--to=philip.li@intel.com \
--cc=cheng.lin130@zte.com.cn \
--cc=davem@davemloft.net \
--cc=kbuild-all@01.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=wang.liang82@zte.com.cn \
--cc=wang.yi59@zte.com.cn \
--cc=xue.zhihong@zte.com.cn \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.