From: Florian Westphal <fw@strlen.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
David Miller <davem@davemloft.net>,
syzkaller-bugs@googlegroups.com, netdev <netdev@vger.kernel.org>,
Florian Westphal <fw@strlen.de>
Subject: Re: syzcaller patch postings...
Date: Thu, 22 Feb 2018 11:03:10 +0100 [thread overview]
Message-ID: <20180222100310.GD24858@breakpoint.cc> (raw)
In-Reply-To: <CACT4Y+Ywzk8y1MUmrNsFjLSFTf8xgGiujnPSjwxF9c6eBVMyuQ@mail.gmail.com>
Dmitry Vyukov <dvyukov@google.com> wrote:
> On Thu, Feb 22, 2018 at 9:26 AM, Paolo Abeni <pabeni@redhat.com> wrote:
> > On Wed, 2018-02-21 at 16:47 -0500, David Miller wrote:
> >> I have to mention this now before it gets out of control.
> >>
> >> I would like to ask that syzkaller stop posting the patch it is
> >> testing when it posts to netdev.
> >
> > There is an open issue on this topic:
> >
> > https://github.com/google/syzkaller/issues/526
> >
> > The current behaviour is that syzbot replies to all get_maintainer.pl
> > recipients after testing a patch, regardless of the test submission
> > recipient list, the idea was instead to respect such list.
>
>
> Hi David, Florian, Paolo,
>
> Didn't realize it triggers patchwork. This wasn't intentional, sorry.
>
> Do I understand it correctly that if syzbot replies to the CC list
> that was in the testing request, it will resolve the problem? So if
> netdev wasn't in CC, it will not be added to CC.
Yes, thats at least my expected/desired behaviour.
This way I can even CC some other person (maintainer, reporter etc)
to have them informed about test result too.
> I will go and fix it now.
Thank you Dmitry!
next prev parent reply other threads:[~2018-02-22 10:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 21:47 syzcaller patch postings David Miller
2018-02-21 21:52 ` Florian Westphal
2018-02-22 8:26 ` Paolo Abeni
2018-02-22 9:58 ` Dmitry Vyukov
2018-02-22 10:03 ` Florian Westphal [this message]
2018-02-22 12:59 ` Dmitry Vyukov
2018-02-22 13:31 ` Daniel Axtens
2018-02-22 13:54 ` Dmitry Vyukov
2018-02-22 14:16 ` Daniel Axtens
2018-02-22 14:39 ` Dmitry Vyukov
2018-02-22 14:35 ` David Miller
2018-02-22 14:46 ` Dmitry Vyukov
2018-02-22 15:09 ` Daniel Axtens
2018-02-23 10:30 ` Dmitry Vyukov
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=20180222100310.GD24858@breakpoint.cc \
--to=fw@strlen.de \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
/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.