On 4/26/18 4:26 AM, Linus Walleij wrote:
The patches need to be applied for v4.18 unless you can state a technical reason why they should go into v4.17.
Patch #1 is definitely a fix because 4.17 adds Stehpen's sparse GPIO support, but without patch #1, that support is broken.
Without patch #2, you can't register more than one TLMM device. Currently, no driver does that, so it's a fix, but not for a regression.
Patch #2 is new support. I guess that's for 4.18 now.
Technical reasons for patches at this point means that it is fixing a regression present in v4.17-rc1. Impatience is sadly not a technical reason ... trust me that I as human understand that very well, but as subsystem maintainer I have responsibilities with regards to the process.
I understand all that, but my patches were posted on the list long before the merge window opened. I consider them part of Stephen's patch set, which was merged for 4.17.
-- Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project. -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
