|
From: Andrew M. <ak...@li...> - 2018-07-18 02:11:54
|
On Sat, 14 Jul 2018 03:48:35 +0200 Dominique Martinet <asm...@co...> wrote: > Andrew Morton wrote on Fri, Jul 13, 2018: > > On Wed, 11 Jul 2018 10:13:21 +0200 Dominique Martinet <asm...@co...> wrote: > > > I've gathered the currently submitted 9P patches that have reached > > > agreement and will keep this branch up to date: > > > > > > git://github.com/martinetd/linux 9p-next > > > [...] > > > > > > - This is based on v4.18-rc4 with a couple of unrelated patches (an > > > i915 compiler warning-treated-as-error fix and Jun Piao's refcount of > > > trans_mod fix that I would like to see merged before these; both will be > > > removed before actual submission) > > > > Please get this into linux-next after the 4.19-rc1 release. I'll send > > any leftovers I have over to you once this is done. > > Okay, I will rebase onto 4.19-rc1 and send Stephen a pull request for > linux-next at that time (and a second one to linus after getting your > leftovers in + a few days?) > > (I assume the reason to not do that after 4.18 is out is to not > duplicate any patch you might already have gotten merged for 4.19?) > Well, we're at 4.18-rc5 now. In 2-3 weeks Linus will release 4.18 then two weeks after that he'll release 4.19-rc1. But what the heck - I'll send it all at you right now: fs-9p-adding-new-return-type-vm_fault_t.patch net-9p-clientc-add-missing-n-at-the-end-of-p9_debug.patch 9p-net-protocolc-return-enomem-when-kmalloc-failed.patch net-9p-fix-error-path-of-p9_virtio_probe.patch 9p-fix-spelling-mistake-uknown-unknown.patch version-pointer-uninitialized.patch please merge them, ask Stephen to add your tree to linux-next. When the above patches turn up in -next I'll autodrop my copies. |