From: Greg KH <gregkh@linuxfoundation.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Steve French <smfrench@gmail.com>,
Sasha Levin <sashal@kernel.org>,
lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@kernel.org>
Subject: Re: [LSF/MM TOPIC] FS, MM, and stable trees
Date: Wed, 13 Feb 2019 08:37:07 +0100 [thread overview]
Message-ID: <20190213073707.GA2875@kroah.com> (raw)
In-Reply-To: <CAOQ4uxjMYWJPF8wFF_7J7yy7KCdGd8mZChfQc5GzNDcfqA7UAA@mail.gmail.com>
On Wed, Feb 13, 2019 at 09:20:00AM +0200, Amir Goldstein wrote:
> I never saw an email from you or Greg saying, the branch "stable-xxx" is
> in review. Please run your tests.
That is what my "Subject: [PATCH 4.9 000/137] 4.9.156-stable review"
type emails are supposed to kick off. They are sent both to the stable
mailing list and lkml.
This message already starts the testing systems going for a number of
different groups out there, do you want to be added to the cc: list so
you get them directly?
thanks,
greg k-h
next prev parent reply other threads:[~2019-02-13 7:37 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 17:00 [LSF/MM TOPIC] FS, MM, and stable trees Sasha Levin
2019-02-12 21:32 ` Steve French
2019-02-13 7:20 ` Amir Goldstein
2019-02-13 7:37 ` Greg KH [this message]
2019-02-13 9:01 ` Amir Goldstein
2019-02-13 9:18 ` Greg KH
2019-02-13 19:25 ` Sasha Levin
2019-02-13 19:52 ` Greg KH
2019-02-13 20:14 ` James Bottomley
2019-02-15 1:50 ` Sasha Levin
2019-02-15 2:48 ` James Bottomley
2019-02-16 18:28 ` Theodore Y. Ts'o
2019-02-21 15:34 ` Luis Chamberlain
2019-02-21 18:52 ` Theodore Y. Ts'o
2019-03-20 3:46 ` Jon Masters
2019-03-20 5:06 ` Greg KH
2019-03-20 6:14 ` Jon Masters
2019-03-20 6:28 ` Greg KH
2019-03-20 6:32 ` Jon Masters
2022-03-08 9:32 ` Amir Goldstein
2022-03-08 10:08 ` Greg KH
2022-03-08 11:04 ` Amir Goldstein
2022-03-08 15:42 ` Luis Chamberlain
2022-03-08 19:06 ` Sasha Levin
2022-03-09 18:57 ` Luis Chamberlain
2022-03-11 5:23 ` Theodore Ts'o
2022-03-11 12:00 ` Jan Kara
2022-03-11 20:52 ` Luis Chamberlain
2022-03-11 22:04 ` Theodore Ts'o
2022-03-11 22:36 ` Luis Chamberlain
2022-04-27 18:58 ` Amir Goldstein
2022-05-01 16:25 ` Luis Chamberlain
2022-03-10 23:59 ` Steve French
2022-03-11 0:36 ` Chuck Lever III
2022-03-11 20:54 ` Luis Chamberlain
2022-03-08 16:40 ` Theodore Ts'o
2022-03-08 17:16 ` Amir Goldstein
2022-03-09 0:43 ` Dave Chinner
2022-03-09 18:41 ` Luis Chamberlain
2022-03-09 18:49 ` Josef Bacik
2022-03-09 19:00 ` Luis Chamberlain
2022-03-09 21:19 ` Josef Bacik
2022-03-10 1:28 ` Luis Chamberlain
2022-03-10 18:51 ` Josef Bacik
2022-03-10 22:41 ` Luis Chamberlain
2022-03-11 12:09 ` Jan Kara
2022-03-11 18:32 ` Luis Chamberlain
2022-03-12 2:07 ` Luis Chamberlain
2022-03-14 22:45 ` btrfs profiles to test was: (Re: [LSF/MM TOPIC] FS, MM, and stable trees) Luis Chamberlain
2022-03-15 14:23 ` Josef Bacik
2022-03-15 17:42 ` Luis Chamberlain
2022-03-29 20:24 ` [LSF/MM TOPIC] FS, MM, and stable trees Amir Goldstein
2022-04-10 15:11 ` Amir Goldstein
2022-03-08 10:54 ` Jan Kara
2022-03-09 0:02 ` Dave Chinner
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=20190213073707.GA2875@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=sashal@kernel.org \
--cc=smfrench@gmail.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 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.