Re: Removal of GENERIC_GPIO breaks -next

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 17, 2013 at 9:07 PM, Vineet Gupta
<Vineet.Gupta1@xxxxxxxxxxxx> wrote:
> On 04/17/2013 04:07 PM, Alexandre Courbot wrote:
>>
>> Also arch/arc/plat-tb10x/Kconfig now defines GENERIC_GPIO, this will
>> not cause breakage but should not be here anymore (ideally removed by
>> the "Remove GENERIC_GPIO config option" patch)
>>
>> Apart from these two issues, things seem to have gone fine, but I'm
>> not sure how they should be addressed and by who?
>
> For the arc issue - I thought we'd come to consensus already. Quoting your earlier
> email:
>
> "If the only reference to GENERIC_GPIO in your architecture or drivers is the
> declaration of this config option, then it is perfectly fine - I will take care of
> removing it when the time is right."
>
> Anyhow it's a minor issue - since your code is in -next, maybe you can add the
> following patch to your branch - rather than routing via my tree - better for
> bisectablity. I compile tested here !

Yes, I am not too worried about arc since it doesn't break anything.
But as you mention it would be better if the whole job could be done
by the same patch. The problem here is the merge order, for me to
address this I need to work after your patches. So maybe in the end my
series should be merged at the end of the merge window, and after all
architecture code is merged, to make sure I can address all instances.

Alex.
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux