From: Peter Nørlund
Date: Mon, 5 Oct 2015 23:31:58 +0200
> What is the proper way to supply fixes for this kind of errors? Should
> I submit the original patches again with the bug fixed, or should I
> submit a patch fixing this particular problem? I imagine bisecting
> becomes annoying when a pa
Peter Nørlund wrote:
> What is the proper way to supply fixes for this kind of errors? Should
> I submit the original patches again with the bug fixed, or should I
> submit a patch fixing this particular problem?
The latter, relative fix, with 'Fixes: ("name of commit") tag'.
--
To unsubscribe f
On Mon, 05 Oct 2015 04:26:38 -0700 (PDT)
David Miller wrote:
> From: kbuild test robot
> Date: Mon, 5 Oct 2015 18:54:18 +0800
>
> > tree:
> > https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
> > master head: 937317c7c1097aa878a5000e3aab616eb5c590c0 commit:
> > 0e884c78ee19e9
From: kbuild test robot
Date: Mon, 5 Oct 2015 18:54:18 +0800
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
> master
> head: 937317c7c1097aa878a5000e3aab616eb5c590c0
> commit: 0e884c78ee19e902f300ed147083c28a0c6302f0 [647/682] ipv4: L3
> hash-based multipath
> co
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
master
head: 937317c7c1097aa878a5000e3aab616eb5c590c0
commit: 0e884c78ee19e902f300ed147083c28a0c6302f0 [647/682] ipv4: L3 hash-based
multipath
config: i386-defconfig (attached as .config)
reproduce:
git checkout
