public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>, viro@zeniv.linux.org.uk
Cc: dhowells@redhat.com, Stephen Rothwell <sfr@canb.auug.org.au>,
	syzbot <syzbot+762a577f56cfb1574647@syzkaller.appspotmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Levin, Alexander" <alexander.levin@verizon.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux@dominikbrodowski.net,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	nikolaus.voss@loewensteinmedical.de,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: linux-next boot error (2)
Date: Tue, 27 Nov 2018 10:25:30 +0000	[thread overview]
Message-ID: <30486.1543314330@warthog.procyon.org.uk> (raw)
In-Reply-To: <CACT4Y+boXfNjHT1M5B6OttHiUFKsvL7AFH2Gfd+DbkNoQD4YVg@mail.gmail.com>

Dmitry Vyukov <dvyukov@google.com> wrote:

> Please either use the Reported-by tag (for amended linux-next fixes
> Tested-by can make more sense and is recognized too), or tell syzbot
> separately:

It got folded in as that's better than carrying a separate patch.

I'll ask Al how he wants to deal with this since he's carrying the patches
now.

David

  reply	other threads:[~2018-11-27 10:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06  8:21 linux-next boot error (2) syzbot
2018-09-06  8:41 ` David Howells
2018-09-06  8:52   ` Dmitry Vyukov
2018-09-11 20:16     ` David Howells
2018-09-11 20:34       ` Stephen Rothwell
2018-09-11 21:24         ` David Howells
2018-11-21 13:32           ` Dmitry Vyukov
2018-11-27 10:25             ` David Howells [this message]
2018-11-27 10:38               ` 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=30486.1543314330@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.levin@verizon.com \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=nikolaus.voss@loewensteinmedical.de \
    --cc=sfr@canb.auug.org.au \
    --cc=syzbot+762a577f56cfb1574647@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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