* [GIT PULL] f2fs fixes for v4.6-rc3 @ 2016-04-04 5:21 Jaegeuk Kim 2016-04-04 20:07 ` Linus Torvalds 0 siblings, 1 reply; 3+ messages in thread From: Jaegeuk Kim @ 2016-04-04 5:21 UTC (permalink / raw) To: Linus Torvalds Cc: Linux Kernel Mailing List, Linux FS Dev Mailing List, Linux F2FS Dev Mailing List Hi Linus, Could you please pull the below commits for v4.6-rc3? Thanks, The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca: Linux 4.6-rc1 (2016-03-26 16:03:24 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-linus for you to fetch changes up to b2dde6fca37e947628b82ae8f35e183ff112d07c: f2fs: retrieve IO write stat from the right place (2016-03-30 13:21:16 -0700) ---------------------------------------------------------------- Jaegeuk Kim (2): f2fs: cover large section in sanity check of super f2fs crypto: fix corrupted symlink in encrypted case Shuoran Liu (1): f2fs: retrieve IO write stat from the right place fs/f2fs/namei.c | 12 +++---- fs/f2fs/super.c | 104 +++++++++++++++++++++++++++++++++++--------------------- 2 files changed, 72 insertions(+), 44 deletions(-) ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [GIT PULL] f2fs fixes for v4.6-rc3 2016-04-04 5:21 [GIT PULL] f2fs fixes for v4.6-rc3 Jaegeuk Kim @ 2016-04-04 20:07 ` Linus Torvalds 2016-04-04 21:15 ` Jaegeuk Kim 0 siblings, 1 reply; 3+ messages in thread From: Linus Torvalds @ 2016-04-04 20:07 UTC (permalink / raw) To: Jaegeuk Kim Cc: Linux Kernel Mailing List, Linux FS Dev Mailing List, Linux F2FS Dev Mailing List On Sun, Apr 3, 2016 at 10:21 PM, Jaegeuk Kim <jaegeuk@kernel.org> wrote: > > Could you please pull the below commits for v4.6-rc3? Pulled, but.. > git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-linus .. the above is a tag, but it's not signed, nor even annotated. So it has no message about what the fixes are in it, it's just the plain SHA1 id. Now, I don't really require signed tags from kernel.org, but it would still be nice. And I *do* want a little blurb about the fixes, even if it doesn't have to be all that exhaustive. Putting that in the tag is convenient, but I'm ok with it being just in the email message too, like you usually do. This case had neither, so now my merge message is not as descriptive as I prefer them ;( Linus ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [GIT PULL] f2fs fixes for v4.6-rc3 2016-04-04 20:07 ` Linus Torvalds @ 2016-04-04 21:15 ` Jaegeuk Kim 0 siblings, 0 replies; 3+ messages in thread From: Jaegeuk Kim @ 2016-04-04 21:15 UTC (permalink / raw) To: Linus Torvalds Cc: Linux Kernel Mailing List, Linux FS Dev Mailing List, Linux F2FS Dev Mailing List On Mon, Apr 04, 2016 at 01:07:11PM -0700, Linus Torvalds wrote: > On Sun, Apr 3, 2016 at 10:21 PM, Jaegeuk Kim <jaegeuk@kernel.org> wrote: > > > > Could you please pull the below commits for v4.6-rc3? > > Pulled, but.. > > > git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-linus > > .. the above is a tag, but it's not signed, nor even annotated. So it > has no message about what the fixes are in it, it's just the plain > SHA1 id. > > Now, I don't really require signed tags from kernel.org, but it would > still be nice. And I *do* want a little blurb about the fixes, even if > it doesn't have to be all that exhaustive. Putting that in the tag is > convenient, but I'm ok with it being just in the email message too, > like you usually do. Definitely, will do. Thank you for pulling the patches. Thanks, > > This case had neither, so now my merge message is not as descriptive > as I prefer them ;( > > Linus ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-04-04 21:15 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2016-04-04 5:21 [GIT PULL] f2fs fixes for v4.6-rc3 Jaegeuk Kim 2016-04-04 20:07 ` Linus Torvalds 2016-04-04 21:15 ` Jaegeuk Kim
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).