From: Minchan Kim <minchan@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, axboe@kernel.dk, hch@lst.de,
sfr@canb.auug.org.au, mm-commits@vger.kernel.org
Subject: Re: + zram-mm-vs-block.patch added to -mm tree
Date: Mon, 28 Aug 2017 17:23:10 +0900 [thread overview]
Message-ID: <20170828082310.GA6867@blaptop> (raw)
In-Reply-To: <59a0805d.+Stgs7t+IN2CkqZt%akpm@linux-foundation.org>
On Fri, Aug 25, 2017 at 12:54:05PM -0700, akpm@linux-foundation.org wrote:
>
> The patch titled
> Subject: zram-mm-vs-block
> has been added to the -mm tree. Its filename is
> zram-mm-vs-block.patch
>
> This patch should soon appear at
> http://ozlabs.org/~akpm/mmots/broken-out/zram-mm-vs-block.patch
> and later at
> http://ozlabs.org/~akpm/mmotm/broken-out/zram-mm-vs-block.patch
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> The -mm tree is included into linux-next and is updated
> there every 3-4 working days
>
> ------------------------------------------------------
> From: Andrew Morton <akpm@linux-foundation.org>
> Subject: zram-mm-vs-block
>
> resolve interface changes from block tree
>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Minchan Kim <minchan@kernel.org>
> Cc: Jens Axboe <axboe@kernel.dk>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Thanks for the handling this issue, Andrew and Christoph!
parent reply other threads:[~2017-08-28 8:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <59a0805d.+Stgs7t+IN2CkqZt%akpm@linux-foundation.org>]
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=20170828082310.GA6867@blaptop \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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