Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1211215
| From | Chris Mason <clm@fb.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next conflict resolution branch for btrfs |
| Date | 2015-08-21 17:30 +0200 |
| Message-ID | <pZWqu-7Av-13@gated-at.bofh.it> (permalink) |
| References | <pZBYK-3iA-15@gated-at.bofh.it> <pZIGS-4zi-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Aug 21, 2015 at 10:45:24AM +1000, Stephen Rothwell wrote: > Hi Chris, > > On Thu, 20 Aug 2015 13:39:18 -0400 Chris Mason <clm@fb.com> wrote: > > > > There are a few conflicts for btrfs in linux-next this time. They are > > small, but I pushed out the merge commit I'm using here: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git next-merge > > Thanks for that. It seems to have merged OK but maybe it conflicts > with something later in linux-next. Unfortunately see my other email > about a build problem. I will keep this example merge in mind for > later. Ok, sorry about that one. We probably want the ifdefs up in Tejun's code, but I'll talk with him about it today and get it fixed up. Thanks, Chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
linux-next conflict resolution branch for btrfs Chris Mason <clm@fb.com> - 2015-08-20 19:40 +0200
Re: linux-next conflict resolution branch for btrfs Stephen Rothwell <sfr@canb.auug.org.au> - 2015-08-21 02:50 +0200
Re: linux-next conflict resolution branch for btrfs Chris Mason <clm@fb.com> - 2015-08-21 17:30 +0200
Re: linux-next conflict resolution branch for btrfs Chris Mason <clm@fb.com> - 2015-08-21 20:10 +0200
csiph-web