On Friday 16 September 2016 11:06 PM, Mark Brown wrote:
On Fri, Sep 16, 2016 at 09:51:38PM +0530, Keerthy wrote:
On Friday 16 September 2016 07:01 PM, Mark Brown wrote:
On Fri, Sep 16, 2016 at 05:12:38PM +0530, Keerthy wrote:
Should i repost this series? I do not see this series in linux-next yet.
Please don't send content free pings and please allow a reasonable time
for review. People get busy, go on holiday, attend conferences and so
I should have been clearer.
The last Lee Jones conveyed that:
"I can't take this series yet, since it relies on a change which was
taken into Mark's Regulator tree"
https://lkml.org/lkml/2016/8/31/312
So wanted to check if i needed to re-base/repost this series again.
Sorry about the confusion i think that is because of $Subject goof up in the
0th patch of the series.
I'm afraid I've no real idea what this series is about or what patches
it might depend on, sorry. If you're waiting for me to do something
you'll need to tell me what it is but if it's a dependency that needs
cross merging then reposting this series isn't going to be needed.
The series cleans up mainly the regulator driver and implements
the device tree parsing using the regulator framework. Removes
all the redundant compatibles for the individual regulators.
Adds platform_device_id table for the gpio and power button modules.
This has been reviewed extensively.
Looks like v7 no longer applies directly on the linux-next branch as it
conflicts with:
https://kernel.googlesource.com/pub/scm/linux/kernel/git/dtor/input/+/722dc54628ca5cffd3b4581b523775aa422b55df
I will rebase and repost on the current linux-next and post v8.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
