From: David Miller <davem@davemloft.net>
To: dvyukov@google.com
Cc: pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
netdev@vger.kernel.org, fw@strlen.de
Subject: Re: syzcaller patch postings...
Date: Thu, 22 Feb 2018 09:35:16 -0500 (EST) [thread overview]
Message-ID: <20180222.093516.144747386298055475.davem@davemloft.net> (raw)
In-Reply-To: <CACT4Y+Ywzk8y1MUmrNsFjLSFTf8xgGiujnPSjwxF9c6eBVMyuQ@mail.gmail.com>
From: Dmitry Vyukov <dvyukov@google.com>
Date: Thu, 22 Feb 2018 10:58:07 +0100
> 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.
>
> I will go and fix it now.
I don't want syzbot to send the patch to netdev, even if it
was in the CC: list.
And again this goes for netfilter-devel and linux-wireless as
well.
There is no reason whatsoever for syzbot to ever post an already
posted patch back to the list again, even if it was on the CC:
list.
In fact netdev will be on that CC: list most of the time.
next prev parent reply other threads:[~2018-02-22 14:35 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
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 [this message]
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=20180222.093516.144747386298055475.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=fw@strlen.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).