diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2018-02-22 12:53:31 +0100 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2018-02-22 13:08:34 +0100 |
| commit | 7daaa06d53f0f496aa1a87656d16c81ebff37f73 (patch) | |
| tree | 6648bf4e9b95724e61010fa9e3294e341773f4af /docs/syzbot.md | |
| parent | 04cbdbd1ae105f4d9f11fda99b588168cec2b3a8 (diff) | |
dashboard/app: restrict patch testing result CC list
Currently dashboard sends patch testing result to full bug CC list
(which includes kernel mailing lists). This is unnecessary and causes
problems with patchwork.
Reply only to people in the testing request CC list
(adding our mailing list if it was missing).
Fixes #526
Diffstat (limited to 'docs/syzbot.md')
| -rw-r--r-- | docs/syzbot.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/syzbot.md b/docs/syzbot.md index ab3763e9b..e239a9e12 100644 --- a/docs/syzbot.md +++ b/docs/syzbot.md @@ -39,6 +39,8 @@ reliable because of email clients splitting lines and messing with whitespaces. `syzbot` will test the patch on `HEAD` of the specified git repo/branch. Note: this can be used both for testing fix patches and just for debugging (i.e. adding additional checks to code and testing with them). +Note: you may send the request only to `syzbot` email address, as patches sent +to some mailing lists (e.g. netdev, netfilter-devel) will trigger patchwork. After sending an email you should get a reply email with results within an hour. - to mark the bug as a duplicate of another `syzbot` bug: ``` |