Hi Egil, Egil Hjelmeland <privat@xxxxxxxxxxxxxxxxxx> writes: >> I'd suggest you to split up this one commit in several *atomic* and easy >> to review patches and send them separately as on thread named "net: dsa: >> lan9303: fix MDIO interface" (also note that imperative is prefered for >> subject lines, see: https://chris.beams.io/posts/git-commit/#imperative) > > I can split the first patch. > > I can also split the patch series to more digestible series. But > since most of the patches touches the same file, I assume that each > series must be completed and applied before starting on a new one. > So I really want to group the patches into only a few series in order > to not spend months on the process. I understand. But believe me, your patches are very likely to land mainline faster if you send them in small chunks. This might not be true for every subsystems, but netdev is very responsive. This is even more true since this series has no-no (such as the sysfs entries) which guarantees the whole patch series to be rejected. Sending portions of your local work branch then rebase it against net-next/master is a usual development process. Thanks, Vivien -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
