On Wed, Mar 21, 2018 at 05:13:10PM +0100, Florian Westphal wrote: > Phil Sutter <phil@xxxxxx> wrote: > > > This is clashing with existing fixes in nf.git. > > TBH, I never know which kernel to test against. Candidates usually are > > nf-next, nf, net-next and sometimes even net. Probably business as > > usual, or do you have a suggestion as to what I should "default" to? > > If its netfilter related and not a bug fix, use nf-next. > If its a bug fix, then always use nf.git unless the bug is only > present in nf-next. > > Otherwise, same applies to net tree for general network bugs. OK, thanks. I realize I was aware of that already, but the fact that sometimes a fix exists in nf but not in nf-next means I have to check both trees. The culprit here is that my VM script (minime, which I gave you once) doesn't support that yet. Something I should fix. Thanks, Phil -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
