From: Alexander Duyck <alexander.duyck@xxxxxxxxx> Date: Fri, 28 Oct 2016 08:48:01 -0700 > So the feedback for this set has been mostly just a few "Acked-by"s, > and it looks like the series was marked as "Not Applicable" in > patchwork. I was wondering what the correct merge strategy for this > patch set should be going forward? I marked it as not applicable because it's definitely not a networking change, and merging it via my tree would be really inappropriate, even though we need it for some infrastructure we want to build for networking. So you have to merge this upstream via a more appropriate path. > I was wondering if I should be looking at breaking up the set and > splitting it over a few different trees, or if I should just hold onto > it and resubmit it when the merge window opens? My preference would > be to submit it as a single set so I can know all the patches are > present to avoid any possible regressions due to only part of the set > being present. I don't think you need to split it up. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>