[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-id: <008501d0348b$a52b4800$ef81d800$@samsung.com>
Date: Tue, 20 Jan 2015 16:30:50 +0800
From: Chao Yu <chao2.yu@...sung.com>
To: 'Jaegeuk Kim' <jaegeuk@...nel.org>,
'Changman Lee' <cm224.lee@...sung.com>
Cc: linux-kernel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net
Subject: RE: [f2fs-dev] [RFC PATCH 01/10] f2fs: move ext_lock out of struct
extent_info
Ping, any comments on this RFC patch set?
Thanks,
> -----Original Message-----
> From: Chao Yu [mailto:chao2.yu@...sung.com]
> Sent: Monday, January 12, 2015 3:09 PM
> To: Jaegeuk Kim; Changman Lee
> Cc: linux-kernel@...r.kernel.org; linux-f2fs-devel@...ts.sourceforge.net
> Subject: [f2fs-dev] [RFC PATCH 01/10] f2fs: move ext_lock out of struct extent_info
>
> Move ext_lock out of struct extent_info, then in the following patches we can
> use variables with struct extent_info type as a parameter to pass pure data.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists