docs: update the patch testing documentation

Add an example of an inlined patch testing request.
Add a link to the real-word #syz test commands.
Remove the mention of delays due to bisections -- it's no longer the
case.

1 files changed, 18 insertions, 3 deletions

diff --git a/docs/syzbot.md b/docs/syzbot.md
index fef169a14..c3a84621b 100644
--- a/docs/syzbot.md
+++ b/docs/syzbot.md
@@ -82,18 +82,33 @@ or alternatively, to test on exact commit reply with:
 ```
 #syz test: git://repo/address.git commit-hash
 ```
+
 If you also provide a patch with the email, `syzbot` will apply it on top of the
-tree before testing. The patch can be provided either inline in email text or as
+tree before testing. The patch can be provided inline in email text or as
 a text attachment (which is more reliable if your email client messes with
 whitespaces).
 
+If you want to include the patch directly in the email body, just paste the diff
+somewhere under the `#syz test` command line, e.g.
+
+```
+#syz test: git://repo/address.git branch
+
+--- a/mm/kasan/kasan.c
++++ b/mm/kasan/kasan.c
+-       current->kasan_depth++;
++       current->kasan_depth--;
+```
+
+[Here](https://groups.google.com/g/syzkaller-bugs/search?q=%22%23syz%20test%22) are
+some real examples of `#syz test` commands for syzbot-reported bugs.
+
 If you don't provide a patch, `syzbot` will test the tree as is.
 This is useful if this is your own tree which already contains the patch,
 or to check if the bug is already fixed by some recent commit.
 
 After sending an email you should typically get a reply email with results within
-an hour. In certain cases (e.g. syzbot is busy with a bisection) it might take
-singnificantly longer, up to a few days (see #1923 for details).
+an hour.
 
 **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.