From: "Theodore Ts'o" <tytso@mit.edu>
To: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Cc: linux-block@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, axboe@kernel.dk,
adilger.kernel@dilger.ca, jaegeuk@kernel.org, chao@kernel.org,
johannes.thumshirn@wdc.com, damien.lemoal@wdc.com,
bvanassche@acm.org, dongli.zhang@oracle.com, clm@fb.com,
ira.weiny@intel.com, dsterba@suse.com, ebiggers@kernel.org,
hch@infradead.org, dave.hansen@intel.com
Subject: Re: [RFC PATCH 6/8] ext4: use memcpy_to_page() in pagecache_write()
Date: Thu, 25 Mar 2021 10:22:54 -0400 [thread overview]
Message-ID: <YFycvk4aMoPAZcwJ@mit.edu> (raw)
In-Reply-To: <20210207190425.38107-7-chaitanya.kulkarni@wdc.com>
On Sun, Feb 07, 2021 at 11:04:23AM -0800, Chaitanya Kulkarni wrote:
> Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
> ---
> fs/ext4/verity.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
Hi, were you expecting to have file system maintainers take these
patches into their own trees? The ext4 patches look good, and unless
you have any objections, I can take them through the ext4 tree.
Thanks,
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Ts'o" <tytso@mit.edu>
To: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Cc: axboe@kernel.dk, ebiggers@kernel.org, damien.lemoal@wdc.com,
bvanassche@acm.org, hch@infradead.org,
johannes.thumshirn@wdc.com, dave.hansen@intel.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-block@vger.kernel.org, clm@fb.com,
adilger.kernel@dilger.ca, dongli.zhang@oracle.com,
linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
dsterba@suse.com, linux-ext4@vger.kernel.org,
ira.weiny@intel.com
Subject: Re: [f2fs-dev] [RFC PATCH 6/8] ext4: use memcpy_to_page() in pagecache_write()
Date: Thu, 25 Mar 2021 10:22:54 -0400 [thread overview]
Message-ID: <YFycvk4aMoPAZcwJ@mit.edu> (raw)
In-Reply-To: <20210207190425.38107-7-chaitanya.kulkarni@wdc.com>
On Sun, Feb 07, 2021 at 11:04:23AM -0800, Chaitanya Kulkarni wrote:
> Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
> ---
> fs/ext4/verity.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
Hi, were you expecting to have file system maintainers take these
patches into their own trees? The ext4 patches look good, and unless
you have any objections, I can take them through the ext4 tree.
Thanks,
- Ted
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-03-25 14:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 19:04 [RFC PATCH 0/8] use core page calls instead of kmaps Chaitanya Kulkarni
2021-02-07 19:04 ` [f2fs-dev] " Chaitanya Kulkarni
2021-02-07 19:04 ` [RFC PATCH 1/8] brd: use memcpy_from_page() in copy_from_brd() Chaitanya Kulkarni
2021-02-07 19:04 ` [f2fs-dev] " Chaitanya Kulkarni
2021-02-07 22:34 ` kernel test robot
2021-02-07 19:04 ` [RFC PATCH 2/8] " Chaitanya Kulkarni
2021-02-07 19:04 ` [f2fs-dev] " Chaitanya Kulkarni
2021-02-08 4:35 ` Ira Weiny
2021-02-08 4:35 ` [f2fs-dev] " Ira Weiny
2021-02-08 5:47 ` Chaitanya Kulkarni
2021-02-08 5:47 ` [f2fs-dev] " Chaitanya Kulkarni
2021-02-07 19:04 ` [RFC PATCH 3/8] null_blk: use memcpy_page() in copy_to_nullb() Chaitanya Kulkarni
2021-02-07 19:04 ` [f2fs-dev] " Chaitanya Kulkarni
2021-02-07 19:04 ` [RFC PATCH 4/8] null_blk: use memcpy_page() in copy_from_nullb() Chaitanya Kulkarni
2021-02-07 19:04 ` [f2fs-dev] " Chaitanya Kulkarni
2021-02-07 19:04 ` [RFC PATCH 5/8] ext4: use memcpy_from_page() in pagecache_read() Chaitanya Kulkarni
2021-02-07 19:04 ` [f2fs-dev] " Chaitanya Kulkarni
2021-02-08 1:45 ` kernel test robot
2021-02-07 19:04 ` [RFC PATCH 6/8] ext4: use memcpy_to_page() in pagecache_write() Chaitanya Kulkarni
2021-02-07 19:04 ` [f2fs-dev] " Chaitanya Kulkarni
2021-03-25 14:22 ` Theodore Ts'o [this message]
2021-03-25 14:22 ` Theodore Ts'o
2021-03-25 15:09 ` Ira Weiny
2021-03-25 15:09 ` [f2fs-dev] " Ira Weiny
2021-03-25 15:10 ` Ira Weiny
2021-03-25 15:10 ` [f2fs-dev] " Ira Weiny
2021-02-07 19:04 ` [RFC PATCH 7/8] f2fs: use memcpy_from_page() in pagecache_read() Chaitanya Kulkarni
2021-02-07 19:04 ` [f2fs-dev] " Chaitanya Kulkarni
2021-02-07 19:04 ` [RFC PATCH 8/8] f2fs: use memcpy_to_page() in pagecache_write() Chaitanya Kulkarni
2021-02-07 19:04 ` [f2fs-dev] " Chaitanya Kulkarni
2021-02-10 18:01 ` Eric Biggers
2021-02-10 18:01 ` [f2fs-dev] " Eric Biggers
2021-02-10 19:41 ` Chaitanya Kulkarni
2021-02-10 19:41 ` [f2fs-dev] " Chaitanya Kulkarni
2021-02-07 19:10 ` [RFC PATCH 0/8] use core page calls instead of kmaps Chaitanya Kulkarni
2021-02-07 19:10 ` [f2fs-dev] " Chaitanya Kulkarni
2021-02-08 4:42 ` Ira Weiny
2021-02-08 4:42 ` [f2fs-dev] " Ira Weiny
2021-02-08 5:47 ` Chaitanya Kulkarni
2021-02-08 5:47 ` [f2fs-dev] " Chaitanya Kulkarni
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=YFycvk4aMoPAZcwJ@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=chaitanya.kulkarni@wdc.com \
--cc=chao@kernel.org \
--cc=clm@fb.com \
--cc=damien.lemoal@wdc.com \
--cc=dave.hansen@intel.com \
--cc=dongli.zhang@oracle.com \
--cc=dsterba@suse.com \
--cc=ebiggers@kernel.org \
--cc=hch@infradead.org \
--cc=ira.weiny@intel.com \
--cc=jaegeuk@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.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.