Re: [GIT PULL] 9p changes fro merge window

[Eric Van Hensbergen]

On Tue, Oct 25, 2011 at 3:46 PM, Geert Uytterhoeven
<geert@xxxxxxxxxxxxxx> wrote:
> On Tue, Oct 25, 2011 at 22:23, Eric Van Hensbergen <ericvh@xxxxxxxxx> wrote:
>> On Tue, Oct 25, 2011 at 3:14 PM, Eric Van Hensbergen <ericvh@xxxxxxxxx> wrote:
>>> On Tue, Oct 25, 2011 at 2:25 AM, Linus Torvalds
>>> <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
>>>> On Mon, Oct 24, 2011 at 6:28 PM, Eric Van Hensbergen <ericvh@xxxxxxxxx> wrote:
>>>>
>>>> (Also, I'm only seeing about half the patches mentioned in linux-next. Hmm?)
>>>
>>
>> okay, which linux-next tree are you looking at (and/or which patches
>> are they missing)? If I look at
>> /pub/scm/linux/kernel/git/next/linux-next.git on kernel.org I see all
>> the patches mentioned in my pull.  Sorry in advance if I'm doing
>> something stupid.
>
> Current linux-next is next-20111025, but the previous one was next-20111014.
>

I think I see the requested changes in both of those versions:
   == next-20111025 ==
14211d0 9p: fix 9p.txt to advertise msize instead of maxdata
348b590 net/9p: Convert net/9p protocol dumps to tracepoints
ef6b080 fs/9p: change an int to unsigned int
4d5077f fs/9p: Cleanup option parsing in 9p
5635fd0 9p: move dereference after NULL check
464f5ec fs/9p: inode file operation is properly initialized init_special_inode
abfa034 fs/9p: Update zero-copy implementation in 9p
  == next-20111014 ==
662db18 9p: fix 9p.txt to advertise msize instead of maxdata
ebbfa91 net/9p: Convert net/9p protocol dumps to tracepoints
0c2f0c5 fs/9p: change an int to unsigned int
73bd290 fs/9p: Cleanup option parsing in 9p
99f4122 9p: move dereference after NULL check
402e032 fs/9p: inode file operation is properly initialized init_special_inode
6851475 fs/9p: Update zero-copy implementation in 9p

The ordering was a bit wacky in next-20111014, like stuff had been
shuffled around, but they were all there.

             -eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/