On Thu, Jun 12, 2014 at 10:56 AM, Alexandre Belloni <alexandre.belloni@xxxxxxxxxxxxxxxxxx> wrote: > Hi, > > On 12/06/2014 at 10:37:43 -0700, Bryan Wu wrote : >> On Thu, Jun 12, 2014 at 10:12 AM, Russell King - ARM Linux >> <linux@xxxxxxxxxxxxxxxx> wrote: >> > So, I see this commit in mainline: >> > >> > commit e81d372ff9f694e13fa46e8b5aaed505c7fd2a1f >> > Merge: 75e300c8ba58 2f05e1d4458f >> > Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> >> > Date: Sat Dec 15 12:52:42 2012 -0800 >> > >> >> Are you sure? this was a git pull in 2012. At that time I didn't get >> any patch from you. >> >> The latest pull was >> >> commit 4162877d3ffa900b618c369c490c7faa6af60e47 >> Merge: 6c61403 14f5716 >> Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> >> Date: Thu Apr 10 09:06:10 2014 -0700 >> >> Merge branch 'for-next' of >> git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/linux-leds >> > > This pull request was for 3.15. > >> > Yet I don't see this patch series in it. What's the story behind the >> > lack of progress on this? >> > >> > Your April response clearly indicated that the entire patch set was going >> > in during the 3.16 merge window. >> > >> >> The rest of them are queued in my tree >> http://git.kernel.org/cgit/linux/kernel/git/cooloney/linux-leds.git/log/?h=for-next >> >> And I will send them out during 3.16 merge window but now mainline is >> still 3.15-rc8. I believe this is what we talked about before. >> >> Oh, no, I'm sorry, I messed up 3.16 merge window which is before >> 3.15-rc1 with 3.17 merge window. And I really mean 3.17 merge window >> which is before 3.16-rc1. My bad, I will definitely send them all out >> during 3.17 merge window. >> > > Your for-next branch was in linux-next for a while. You don't seem to > have sent a pull request for 3.16 and the merge window is not closed yet > so you can probably do it now. > > You guys are right. Today I'm not in good status to work. Looks like 3.16 merge window is open , right? I will send out pull request soon, actually that's my plan to do that. -Bryan -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
