No, the patches in question don't depend on anything at all other than
thinkpad-acpi itself. If there were no thinkpad-acpi patches "in
flight" in need to get to mainline soon, there would be no problem at
all... but at least one of them clashes with the SW_RFKILL_ALL patch.
thinkpad-acpi merges through Len Brown because that's probably the best
subsystem for it to be tied to right now. It uses various other
subsystems, like the input layer, hwmon, LEDs and rfkill, but it makes
extremely heavy use of the ACPI subsystem to actually *do* something.
But patches to thinkpad-acpi do not HAVE to always go through Len, as
they never modify anything in ACPI proper.
I would be thankful if you could merge the input layer SW_RFKILL_ALL
patch ASAP through your for_linus branch, as that's probably the fastest
way to get the whole rfkill stack in its way to the linux-next tree.
The SW_RFKILL_ALL patch is the only real dependency of the rfkill
patches on anything. If that gets merged now, I can immediately send
the rfkill stack to wireless-dev AND respin the two thinkpad-acpi
patches that are pending on Len's hands to apply without issues on top
of a tree that already had SW_RADIO renamed.
I will send the SW_RFKILL_ALL patch in a version that applies on top of
Linus git tree to you in a few moments.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
