On Thu, Jan 23, 2020 at 03:04:35PM +0800, m...@kaowomen.cn wrote: > On Thu, Jan 23, 2020 at 06:38:53AM +0000, > kohada.tetsuh...@dc.mitsubishielectric.co.jp wrote: > > Hello, Greg. > > > > Thank you for the quick reply. > > > > > Also the patch does not apply to the linux-next tree at all, so I can't > > > take it. > > The patch I sent was based on the master branch of > > “https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/” > > and its tag was v5.5-rc6. > > > > > Also the patch does not apply to the linux-next tree at all, so I can't > > > take it. Please rebase and resend. > > I will send a new patch based on the latest master branch of > > “https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git”. > > > > > > By the way, could you answer below questions for my sending patches in > > future? > > 1. Which repository and branch should be based when creating a new patch? > > 2. How do I inform you about a base on which I create a patch? > If you like you can add [PATCH -next] to patch title before send it. :)
This applies to networking and not to staging. For staging, always work against linux-next or staging-next. For networking patches sent to Dave Miller, then you have to figure out if the patch applies to [PATCH net] or [PATCH net-next]. Just putting [PATCH -next] because you happen to be working on linux-next is not correct. You have to investigate both networking trees to determine where the patch should be applied. regards, dan carpenter _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
