From: Jens Axboe <axboe@fb.com>
To: Christoph Hellwig <hch@lst.de>, Sasha Levin <sasha.levin@oracle.com>
Cc: <hughd@google.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <tj@kernel.org>, <jack@suse.cz>
Subject: Re: [PATCH] mm: shmem: check for mapping owner before dereferencing
Date: Mon, 23 Feb 2015 09:54:24 -0800 [thread overview]
Message-ID: <54EB6950.6030909@fb.com> (raw)
In-Reply-To: <20150223174912.GA25675@lst.de>
On 02/23/2015 09:49 AM, Christoph Hellwig wrote:
> Looks good,
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
Shall I funnel this through for-linus?
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@fb.com>
To: Christoph Hellwig <hch@lst.de>, Sasha Levin <sasha.levin@oracle.com>
Cc: hughd@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, tj@kernel.org, jack@suse.cz
Subject: Re: [PATCH] mm: shmem: check for mapping owner before dereferencing
Date: Mon, 23 Feb 2015 09:54:24 -0800 [thread overview]
Message-ID: <54EB6950.6030909@fb.com> (raw)
In-Reply-To: <20150223174912.GA25675@lst.de>
On 02/23/2015 09:49 AM, Christoph Hellwig wrote:
> Looks good,
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
Shall I funnel this through for-linus?
--
Jens Axboe
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-02-23 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 10:38 [PATCH] mm: shmem: check for mapping owner before dereferencing Sasha Levin
2015-02-23 10:38 ` Sasha Levin
2015-02-23 17:49 ` Christoph Hellwig
2015-02-23 17:49 ` Christoph Hellwig
2015-02-23 17:54 ` Jens Axboe [this message]
2015-02-23 17:54 ` Jens Axboe
2015-02-23 17:57 ` Christoph Hellwig
2015-02-23 17:57 ` Christoph Hellwig
2015-02-25 21:31 ` Hugh Dickins
2015-02-25 21:31 ` Hugh Dickins
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=54EB6950.6030909@fb.com \
--to=axboe@fb.com \
--cc=hch@lst.de \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.com \
--cc=tj@kernel.org \
/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.