On 01/16/2013 03:46 PM, Greg KH wrote: > On Wed, Jan 16, 2013 at 12:38:35PM +0900, Chanwoo Choi wrote: >>>> OK, I will resend pull-request to include only bugfixes patch in 3.8. >>>> After released v3.8-rc7 or 3.8-rc8 kernel, I will send pull-request of >>>> extcon >>>> to include new feature patches of extcon driver in 3.9. >>> >>> No, you can send me that pull request now as well, I have two different >>> branches, one to go to Linus for this release, and one for the next one. >>> Both of them show up in linux-next. You should have the same. >>> >>> So you can send me two pull requests now, does that make more sense? >>> >> I understand and thanks for your comment. I will resend only one >> pull-request for >> extcon to include it for -next branch. I don't send separate pull-request >> for bugfixes patch. > > Why not send a bugfix pull request? Are none of these for 3.8? If so, > fine, but be sure to go through them to determine this.
I think that it isn't critical bug and relevant to extcon core driver. And The issue is trivial and depend on new feature of max77693 extcon driver. Thank you, Chanwoo Choi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
