Re: Request for tree inclusion
Hi Frederic, On Fri, 11 Jan 2013 02:15:39 +0100 Frederic Weisbecker wrote: > > fw-cputime and fs-sched have been merged so you can now remove these > branches from next. Done. > But fw-nohz remains. In the meantime I have created a branch named nohz/next: > > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git > nohz/next > > This branch currently refers to fw-nohz HEAD (aka nohz/printk-v8) and > this is also the place where I'll gather -next materials in the future > instead of the multiple branches you're currently pulling. > So could you please remove fw-nohz (nohz/printk-v8) as well from -next > but include nohz/next instead? Also done. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgp2gofK3cpwX.pgp Description: PGP signature
Re: Request for tree inclusion
2012/12/3 Frederic Weisbecker : > 2012/12/2 Stephen Rothwell : >> Well, these are a bit late (I expected Linus to release v3.7 today), but >> since Ingo has not piped in over the weekend, I have added them from today >> after the tip tree merge. > > Yeah sorry to submit that so late. Those branches are in pending pull > requests to the -tip tree and I thought about relying on the > propagation of -tip into -next as usual. But Ingo has been very busy > with numa related work during this cycle. So until these branches get > merged in -tip, I'm short-circuiting a bit the -next step before it > becomes too late for the next merge window. > >> >> I have called them fw-cputime, fs-sched and fw-nohz respectively and >> listed you as the only contact in case of problems. > > Ok. > >> If these are to be >> long term trees included in linux-next, I would prefer that you use >> better branch names - otherwise, if they are just short term, please tell >> me to remove them when they are finished with. > > They are definitely short term. I'll tell you once these can be dropped. > > Thanks a lot! Hi Stephen! fw-cputime and fs-sched have been merged so you can now remove these branches from next. But fw-nohz remains. In the meantime I have created a branch named nohz/next: git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git nohz/next This branch currently refers to fw-nohz HEAD (aka nohz/printk-v8) and this is also the place where I'll gather -next materials in the future instead of the multiple branches you're currently pulling. So could you please remove fw-nohz (nohz/printk-v8) as well from -next but include nohz/next instead? Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [GIT PULL] f2fs: request for tree inclusion
On Wednesday 19 December 2012, Anca Emanuel wrote: > > Hi Linus, > > An early prototype of this: > https://wiki.linaro.org/WorkingGroups/Kernel/Specs/flash-file-system-prototype > > Are you still testing it ? The prototype was an earlier and independent work done as an internship in Linaro. It resulted in very valuable insights, some of which ended up being integrated into f2fs, but we decided not to follow up on that work since f2fs is far superior overall and has a dedicated team working on it. There are a few features from the prototype that we might want to add in f2fs, but those can be implemented as compatible changes later. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [GIT PULL] f2fs: request for tree inclusion
Hi Linus, An early prototype of this: https://wiki.linaro.org/WorkingGroups/Kernel/Specs/flash-file-system-prototype Are you still testing it ? On Sun, Dec 16, 2012 at 1:19 AM, Jaegeuk Kim wrote: > Hi Linus, > > I'm seeing that f2fs has not been merged yet. > Could you give me any notice for this? > Management priority, or something else? > > BTW, I have added a couple of bug fixes since "for-3.8-merge". > Which is better sending between [GIT PULL v2] or additional pull request > after merge? > > Thanks, > Jaegeuk Kim > > 2012-12-11 (화), 16:58 +0900, Jaegeuk Kim: >> Hi Linus, >> >> This is the first pull request for tree inclusion of Flash-Friendly File >> System (F2FS) towards the 3.8 merge window. >> >> http://lwn.net/Articles/518718/ >> http://lwn.net/Articles/518988/ >> http://en.wikipedia.org/wiki/F2FS >> >> The f2fs has been in the linux-next tree for a while, and several issues >> have been cleared as described in the signed tag below. >> And also, I've done testing f2fs successfully based on Linux 3.7 with >> the following test scenarios. >> >> - Reliability test: >> Run fsstress on an SSD partition. >> >> - Robustness test: >> Conduct sudden-power-off and examine the fs consistency repeatedly, >> while running a reliability test. >> >> So, please pull the f2fs filesystem. >> If I'm missing any issues or made mistakes, please let me know. >> >> Thanks, >> Jaegeuk Kim >> >> The following changes since commit >> 29594404d7fe73cd80eaa4ee8c43dcc53970c60e: >> >> Linux 3.7 (2012-12-10 19:30:57 -0800) >> >> are available in the git repository at: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git >> tags/for-3.8-merge >> >> for you to fetch changes up to e6aa9f36b2bfd6b30072c07b34f2a24becf1: >> >> f2fs: fix tracking parent inode number (2012-12-11 13:43:45 +0900) >> >> >> Introduce a new file system, Flash-Friendly File System (F2FS), to Linux >> 3.8. >> >> Highlights: >> - Add initial f2fs source codes >> - Fix an endian conversion bug >> - Fix build failures on random configs >> - Fix the power-off-recovery routine >> - Minor cleanup, coding style, and typos patches >> >> Greg Kroah-Hartman (1): >> f2fs: move proc files to debugfs >> >> Huajun Li (1): >> f2fs: fix a typo in f2fs documentation >> >> Jaegeuk Kim (22): >> f2fs: add document >> f2fs: add on-disk layout >> f2fs: add superblock and major in-memory structure >> f2fs: add super block operations >> f2fs: add checkpoint operations >> f2fs: add node operations >> f2fs: add segment operations >> f2fs: add file operations >> f2fs: add address space operations for data >> f2fs: add core inode operations >> f2fs: add inode operations for special inodes >> f2fs: add core directory operations >> f2fs: add xattr and acl functionalities >> f2fs: add garbage collection functions >> f2fs: add recovery routines for roll-forward >> f2fs: update Kconfig and Makefile >> f2fs: update the f2fs document >> f2fs: fix endian conversion bugs reported by sparse >> f2fs: adjust kernel coding style >> f2fs: resolve build failures >> f2fs: cleanup the f2fs_bio_alloc routine >> f2fs: fix tracking parent inode number >> >> Namjae Jeon (10): >> f2fs: fix the compiler warning for uninitialized use of variable >> f2fs: show error in case of invalid mount arguments >> f2fs: remove unneeded memset from init_once >> f2fs: check read only condition before beginning write out >> f2fs: remove unneeded initialization >> f2fs: move error condition for mkdir at proper place >> f2fs: rewrite f2fs_bio_alloc to make it simpler >> f2fs: make use of GFP_F2FS_ZERO for setting gfp_mask >> f2fs: remove redundant call to f2fs_put_page in delete entry >> f2fs: introduce accessor to retrieve number of dentry slots >> >> Sachin Kamat (1): >> f2fs: remove unneeded version.h header file from f2fs.h >> >> Wei Yongjun (1): >> f2fs: remove unused variable >> >> Documentation/filesystems/00-INDEX |2 + >> Documentation/filesystems/f2fs.txt | 421
Re: [GIT PULL] f2fs: request for tree inclusion
Hi Linus, I'm seeing that f2fs has not been merged yet. Could you give me any notice for this? Management priority, or something else? BTW, I have added a couple of bug fixes since "for-3.8-merge". Which is better sending between [GIT PULL v2] or additional pull request after merge? Thanks, Jaegeuk Kim 2012-12-11 (화), 16:58 +0900, Jaegeuk Kim: > Hi Linus, > > This is the first pull request for tree inclusion of Flash-Friendly File > System (F2FS) towards the 3.8 merge window. > > http://lwn.net/Articles/518718/ > http://lwn.net/Articles/518988/ > http://en.wikipedia.org/wiki/F2FS > > The f2fs has been in the linux-next tree for a while, and several issues > have been cleared as described in the signed tag below. > And also, I've done testing f2fs successfully based on Linux 3.7 with > the following test scenarios. > > - Reliability test: > Run fsstress on an SSD partition. > > - Robustness test: > Conduct sudden-power-off and examine the fs consistency repeatedly, > while running a reliability test. > > So, please pull the f2fs filesystem. > If I'm missing any issues or made mistakes, please let me know. > > Thanks, > Jaegeuk Kim > > The following changes since commit > 29594404d7fe73cd80eaa4ee8c43dcc53970c60e: > > Linux 3.7 (2012-12-10 19:30:57 -0800) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git > tags/for-3.8-merge > > for you to fetch changes up to e6aa9f36b2bfd6b30072c07b34f2a24becf1: > > f2fs: fix tracking parent inode number (2012-12-11 13:43:45 +0900) > > > Introduce a new file system, Flash-Friendly File System (F2FS), to Linux > 3.8. > > Highlights: > - Add initial f2fs source codes > - Fix an endian conversion bug > - Fix build failures on random configs > - Fix the power-off-recovery routine > - Minor cleanup, coding style, and typos patches > > Greg Kroah-Hartman (1): > f2fs: move proc files to debugfs > > Huajun Li (1): > f2fs: fix a typo in f2fs documentation > > Jaegeuk Kim (22): > f2fs: add document > f2fs: add on-disk layout > f2fs: add superblock and major in-memory structure > f2fs: add super block operations > f2fs: add checkpoint operations > f2fs: add node operations > f2fs: add segment operations > f2fs: add file operations > f2fs: add address space operations for data > f2fs: add core inode operations > f2fs: add inode operations for special inodes > f2fs: add core directory operations > f2fs: add xattr and acl functionalities > f2fs: add garbage collection functions > f2fs: add recovery routines for roll-forward > f2fs: update Kconfig and Makefile > f2fs: update the f2fs document > f2fs: fix endian conversion bugs reported by sparse > f2fs: adjust kernel coding style > f2fs: resolve build failures > f2fs: cleanup the f2fs_bio_alloc routine > f2fs: fix tracking parent inode number > > Namjae Jeon (10): > f2fs: fix the compiler warning for uninitialized use of variable > f2fs: show error in case of invalid mount arguments > f2fs: remove unneeded memset from init_once > f2fs: check read only condition before beginning write out > f2fs: remove unneeded initialization > f2fs: move error condition for mkdir at proper place > f2fs: rewrite f2fs_bio_alloc to make it simpler > f2fs: make use of GFP_F2FS_ZERO for setting gfp_mask > f2fs: remove redundant call to f2fs_put_page in delete entry > f2fs: introduce accessor to retrieve number of dentry slots > > Sachin Kamat (1): > f2fs: remove unneeded version.h header file from f2fs.h > > Wei Yongjun (1): > f2fs: remove unused variable > > Documentation/filesystems/00-INDEX |2 + > Documentation/filesystems/f2fs.txt | 421 + > fs/Kconfig |1 + > fs/Makefile|1 + > fs/f2fs/Kconfig| 53 ++ > fs/f2fs/Makefile |7 + > fs/f2fs/acl.c | 414 + > fs/f2fs/acl.h | 57 ++ > fs/f2fs/checkpoint.c | 794 > fs/f2fs/data.c | 702 ++ > fs/f2fs/debug.c| 361 > fs/f2fs/dir.c | 672 ++ > fs/f2fs/f2fs.h | 1083 ++ >
[GIT PULL] f2fs: request for tree inclusion
Hi Linus, This is the first pull request for tree inclusion of Flash-Friendly File System (F2FS) towards the 3.8 merge window. http://lwn.net/Articles/518718/ http://lwn.net/Articles/518988/ http://en.wikipedia.org/wiki/F2FS The f2fs has been in the linux-next tree for a while, and several issues have been cleared as described in the signed tag below. And also, I've done testing f2fs successfully based on Linux 3.7 with the following test scenarios. - Reliability test: Run fsstress on an SSD partition. - Robustness test: Conduct sudden-power-off and examine the fs consistency repeatedly, while running a reliability test. So, please pull the f2fs filesystem. If I'm missing any issues or made mistakes, please let me know. Thanks, Jaegeuk Kim The following changes since commit 29594404d7fe73cd80eaa4ee8c43dcc53970c60e: Linux 3.7 (2012-12-10 19:30:57 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/for-3.8-merge for you to fetch changes up to e6aa9f36b2bfd6b30072c07b34f2a24becf1: f2fs: fix tracking parent inode number (2012-12-11 13:43:45 +0900) Introduce a new file system, Flash-Friendly File System (F2FS), to Linux 3.8. Highlights: - Add initial f2fs source codes - Fix an endian conversion bug - Fix build failures on random configs - Fix the power-off-recovery routine - Minor cleanup, coding style, and typos patches Greg Kroah-Hartman (1): f2fs: move proc files to debugfs Huajun Li (1): f2fs: fix a typo in f2fs documentation Jaegeuk Kim (22): f2fs: add document f2fs: add on-disk layout f2fs: add superblock and major in-memory structure f2fs: add super block operations f2fs: add checkpoint operations f2fs: add node operations f2fs: add segment operations f2fs: add file operations f2fs: add address space operations for data f2fs: add core inode operations f2fs: add inode operations for special inodes f2fs: add core directory operations f2fs: add xattr and acl functionalities f2fs: add garbage collection functions f2fs: add recovery routines for roll-forward f2fs: update Kconfig and Makefile f2fs: update the f2fs document f2fs: fix endian conversion bugs reported by sparse f2fs: adjust kernel coding style f2fs: resolve build failures f2fs: cleanup the f2fs_bio_alloc routine f2fs: fix tracking parent inode number Namjae Jeon (10): f2fs: fix the compiler warning for uninitialized use of variable f2fs: show error in case of invalid mount arguments f2fs: remove unneeded memset from init_once f2fs: check read only condition before beginning write out f2fs: remove unneeded initialization f2fs: move error condition for mkdir at proper place f2fs: rewrite f2fs_bio_alloc to make it simpler f2fs: make use of GFP_F2FS_ZERO for setting gfp_mask f2fs: remove redundant call to f2fs_put_page in delete entry f2fs: introduce accessor to retrieve number of dentry slots Sachin Kamat (1): f2fs: remove unneeded version.h header file from f2fs.h Wei Yongjun (1): f2fs: remove unused variable Documentation/filesystems/00-INDEX |2 + Documentation/filesystems/f2fs.txt | 421 + fs/Kconfig |1 + fs/Makefile|1 + fs/f2fs/Kconfig| 53 ++ fs/f2fs/Makefile |7 + fs/f2fs/acl.c | 414 + fs/f2fs/acl.h | 57 ++ fs/f2fs/checkpoint.c | 794 fs/f2fs/data.c | 702 ++ fs/f2fs/debug.c| 361 fs/f2fs/dir.c | 672 ++ fs/f2fs/f2fs.h | 1083 ++ fs/f2fs/file.c | 636 + fs/f2fs/gc.c | 742 +++ fs/f2fs/gc.h | 117 +++ fs/f2fs/hash.c | 97 ++ fs/f2fs/inode.c| 268 ++ fs/f2fs/namei.c| 503 ++ fs/f2fs/node.c | 1764 +++ fs/f2fs/node.h | 353 +++ fs/f2fs/recovery.c | 375 fs/f2fs/segment.c | 1791 fs/f2fs/segment.h | 618 + fs/f2fs/super.c| 657 + fs/f2fs/xattr.c| 440 + fs/f2fs/xattr.h| 145 +++ include/linux/f2fs_fs.h| 413 + include/uapi/linux/magic.h |1 + 29 files changed, 13488 insertions(+) create mode 100644 Doc
Re: Request for tree inclusion
2012/12/2 Stephen Rothwell : > Well, these are a bit late (I expected Linus to release v3.7 today), but > since Ingo has not piped in over the weekend, I have added them from today > after the tip tree merge. Yeah sorry to submit that so late. Those branches are in pending pull requests to the -tip tree and I thought about relying on the propagation of -tip into -next as usual. But Ingo has been very busy with numa related work during this cycle. So until these branches get merged in -tip, I'm short-circuiting a bit the -next step before it becomes too late for the next merge window. > > I have called them fw-cputime, fs-sched and fw-nohz respectively and > listed you as the only contact in case of problems. Ok. > If these are to be > long term trees included in linux-next, I would prefer that you use > better branch names - otherwise, if they are just short term, please tell > me to remove them when they are finished with. They are definitely short term. I'll tell you once these can be dropped. Thanks a lot! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Request for tree inclusion
Hi Frederic, On Sat, 1 Dec 2012 00:09:03 +0100 Frederic Weisbecker wrote: > > Could please include the following branches from my tree in linux-next: > > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git > cputime/adjustment-v2 > > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git > sched/cputime-v2 > > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git > nohz/printk-v8 > > The two first are based on tip:/sched/core > The 3rd is based on upstream. Well, these are a bit late (I expected Linus to release v3.7 today), but since Ingo has not piped in over the weekend, I have added them from today after the tip tree merge. I have called them fw-cputime, fs-sched and fw-nohz respectively and listed you as the only contact in case of problems. If these are to be long term trees included in linux-next, I would prefer that you use better branch names - otherwise, if they are just short term, please tell me to remove them when they are finished with. Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window. You will need to ensure that the patches/commits in your tree/series have been: * submitted under GPL v2 (or later) and include the Contributor's Signed-off-by, * posted to the relevant mailing list, * reviewed by you (or another maintainer of your subsystem tree), * successfully unit tested, and * destined for the current or next Linux merge window. Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary. -- Cheers, Stephen Rothwell s...@canb.auug.org.au Legal Stuff: By participating in linux-next, your subsystem tree contributions are public and will be included in the linux-next trees. You may be sent e-mail messages indicating errors or other issues when the patches/commits from your subsystem tree are merged and tested in linux-next. These messages may also be cross-posted to the linux-next mailing list, the linux-kernel mailing list, etc. The linux-next tree project and IBM (my employer) make no warranties regarding the linux-next project, the testing procedures, the results, the e-mails, etc. If you don't agree to these ground rules, let me know and I'll remove your tree from participation in linux-next. pgpb8lYpvrrwU.pgp Description: PGP signature
