All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Cc: wenxu@ucloud.cn, vladbu@nvidia.com, netdev@vger.kernel.org
Subject: Re: [PATCH v10 net-next 3/3] net/sched: act_frag: add implict packet fragment support.
Date: Fri, 13 Nov 2020 09:04:54 -0800	[thread overview]
Message-ID: <20201113090454.1665f89c@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20201113022522.GH3913@localhost.localdomain>

On Thu, 12 Nov 2020 23:25:22 -0300 Marcelo Ricardo Leitner wrote:
> On Thu, Nov 12, 2020 at 02:20:58PM -0800, Jakub Kicinski wrote:
> > On Thu, 12 Nov 2020 11:24:57 +0800 wenxu@ucloud.cn wrote:  
> > > v7-v10: fix __rcu warning   
> > 
> > Are you reposting stuff just to get it build tested?
> > 
> > This is absolutely unacceptable.  
> 
> I don't know if that's the case, but maybe we could have a shadow
> mailing list just for that? So that bots would monitor and would run
> (almost) the same tests are they do here. Then when patches are posted
> here, a list that people actually subscribe, they are already more
> ready. The bots would have to email an "ok" as well, but that's
> implementation detail already. Not that developers shouldn't test
> before posting, but the bots are already doing some tests that may be
> beyond of what one can think of testing before posting.

The code for the entire system is right here:

https://github.com/kuba-moo/nipa

It depends on a patchwork instance to report results to.

I have a script there to feed patches in locally from a maildir but
haven't tested that in a while so it's probably broken. You can also
just run the build bash script without running the whole bot:

https://github.com/kuba-moo/nipa/blob/master/tests/patch/build_allmodconfig_warn/build_allmodconfig.sh

Hardly rocket science.

I have no preference on what people do to test their code, and I'm
happy to take patches for the bot, too.

But we can't have people posting 11 versions of patches to netdev which
is already too high traffic for people to follow.

Not to mention that someone needs to pay for the CPU cycles of the bot,
and we don't want to block getting results for legitimate patches.

  reply	other threads:[~2020-11-13 17:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12  3:24 [PATCH v10 net-next 0/3] net/sched: fix over mtu packet of defrag in wenxu
2020-11-12  3:24 ` [PATCH v10 net-next 1/3] net/sched: fix miss init the mru in qdisc_skb_cb wenxu
2020-11-12  3:24 ` [PATCH v10 net-next 2/3] net/sched: act_mirred: refactor the handle of xmit wenxu
2020-11-12  3:24 ` [PATCH v10 net-next 3/3] net/sched: act_frag: add implict packet fragment support wenxu
2020-11-12 22:20   ` Jakub Kicinski
2020-11-13  2:25     ` Marcelo Ricardo Leitner
2020-11-13 17:04       ` Jakub Kicinski [this message]
2020-11-14 18:05   ` Cong Wang
2020-11-14 22:46     ` Marcelo Ricardo Leitner
2020-11-16 18:57       ` Cong Wang
2020-11-15 13:05     ` wenxu
2020-11-15 16:26       ` Jamal Hadi Salim
2020-11-16  1:09         ` wenxu
2020-11-16 19:01       ` Cong Wang
2020-11-17  4:01         ` wenxu
2020-11-17 22:43           ` Cong Wang
2020-11-17 23:21             ` wenxu

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=20201113090454.1665f89c@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=vladbu@nvidia.com \
    --cc=wenxu@ucloud.cn \
    /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.