All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com>
Cc: "jslaby@suse.cz" <jslaby@suse.cz>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"ben@decadent.org.uk" <ben@decadent.org.uk>,
	"jforbes@redhat.com" <jforbes@redhat.com>,
	"labbott@redhat.com" <labbott@redhat.com>,
	"stefan.bader@canonical.com" <stefan.bader@canonical.com>,
	"tim.gardner@canonical.com" <tim.gardner@canonical.com>,
	"cascardo@canonical.com" <cascardo@canonical.com>,
	"w@1wt.eu" <w@1wt.eu>, "lizefan@huawei.com" <lizefan@huawei.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dhaval.giani@oracle.com" <dhaval.giani@oracle.com>
Subject: Re: Stable/distro kernel testing in Plumbers 2017
Date: Sat, 24 Jun 2017 06:51:55 +0200	[thread overview]
Message-ID: <20170624045155.GA12495@kroah.com> (raw)
In-Reply-To: <20170623032623.teemrog2on7cknuq@sasha-lappy>

On Fri, Jun 23, 2017 at 03:37:28AM +0000, Levin, Alexander (Sasha Levin) wrote:
> Hi all,
> 
> We were hoping to discuss the state of -stable/distro kernel testing 
> in the Testing & Fuzzing MC in Plumbers 2017.
> 
> Mainly we want to understand what sort of testing is being done, how 
> bug reports are being addressed, and what improvments can we make to 
> improve the process.
> 
> The format is pretty open, we can do a BoF type of discussion and 
> talks as part of the MC if anyone is interested in doing any.
> 
> It would be great to know who is interested in this, and would be able 
> to attend Plumbers (https://www.linuxplumbersconf.org/2017/).

I'll be there and would attend this.

thanks,

greg k-h

  reply	other threads:[~2017-06-24  4:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23  3:37 Stable/distro kernel testing in Plumbers 2017 Levin, Alexander (Sasha Levin)
2017-06-24  4:51 ` gregkh [this message]
2017-09-11 16:40   ` Levin, Alexander (Sasha Levin)
2017-06-24 17:15 ` Ben Hutchings
2017-06-24 17:58 ` Masami Hiramatsu

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=20170624045155.GA12495@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.levin@verizon.com \
    --cc=ben@decadent.org.uk \
    --cc=cascardo@canonical.com \
    --cc=dhaval.giani@oracle.com \
    --cc=jforbes@redhat.com \
    --cc=jslaby@suse.cz \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=stable@vger.kernel.org \
    --cc=stefan.bader@canonical.com \
    --cc=tim.gardner@canonical.com \
    --cc=w@1wt.eu \
    /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.