Prev: how to tweak ARP timer on kernel 2.6.9
Next: Staging: comedi:fix missing KERN_facility level in ni_labpc.c
From: David P. Quigley on 9 Mar 2010 14:50
It looks like your patch is already in the tree as commit
7c0ff870d1ed287504a61ed865f3d728c757436b. We saw this problem before and
Eric fixed it up. I thought it was very odd that you posted this 5
minutes ago and it was already upstream.

Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Greg KH on 9 Mar 2010 14:50
On Tue, Mar 09, 2010 at 02:36:12PM -0500, David P. Quigley wrote:
> It looks like your patch is already in the tree as commit
> 7c0ff870d1ed287504a61ed865f3d728c757436b. We saw this problem before and
> Eric fixed it up. I thought it was very odd that you posted this 5
> minutes ago and it was already upstream.

Yeah, this has already been resolved, did that patch not solve the issue
for you?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: David P. Quigley on 9 Mar 2010 14:50
On Tue, 2010-03-09 at 11:42 -0800, Greg KH wrote:
> On Tue, Mar 09, 2010 at 02:36:12PM -0500, David P. Quigley wrote:
> > It looks like your patch is already in the tree as commit
> > 7c0ff870d1ed287504a61ed865f3d728c757436b. We saw this problem before and
> > Eric fixed it up. I thought it was very odd that you posted this 5
> > minutes ago and it was already upstream.
>
> Yeah, this has already been resolved, did that patch not solve the issue
> for you?
>
> thanks,
>
> greg k-h

I don't see how it couldn't have. The patch he submitted which he says
fixes the problem is the exact same patch that Eric submitted back in
Feb. Its possible that he is using a version of 2.6.33-rc8 that is based
off of a commit before the patch was merged since 2.6.33-rc8 was tagged
on Feb 12th and your commit date in the repo is Feb 16th.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jason Gunthorpe on 9 Mar 2010 15:00
On Tue, Mar 09, 2010 at 02:46:28PM -0500, David P. Quigley wrote:
> On Tue, 2010-03-09 at 11:42 -0800, Greg KH wrote:
> > On Tue, Mar 09, 2010 at 02:36:12PM -0500, David P. Quigley wrote:
> > > It looks like your patch is already in the tree as commit
> > > 7c0ff870d1ed287504a61ed865f3d728c757436b. We saw this problem before and
> > > Eric fixed it up. I thought it was very odd that you posted this 5
> > > minutes ago and it was already upstream.
> >
> > Yeah, this has already been resolved, did that patch not solve the issue
> > for you?
>
> I don't see how it couldn't have. The patch he submitted which he says
> fixes the problem is the exact same patch that Eric submitted back in
> Feb. Its possible that he is using a version of 2.6.33-rc8 that is based
> off of a commit before the patch was merged since 2.6.33-rc8 was tagged
> on Feb 12th and your commit date in the repo is Feb 16th.

Yes, that is correct, I was only looking up to 2.6.33-rc8, I didn't
think to check Linus's head branch, my mistake. It looks to me like
the changeset you pointed to was put in Linus's tree after that tag,
so it is fixed, just not in any tagged kernel.

Thanks for looking at this,
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Greg KH on 9 Mar 2010 15:10
On Tue, Mar 09, 2010 at 12:53:03PM -0700, Jason Gunthorpe wrote:
> On Tue, Mar 09, 2010 at 02:46:28PM -0500, David P. Quigley wrote:
> > On Tue, 2010-03-09 at 11:42 -0800, Greg KH wrote:
> > > On Tue, Mar 09, 2010 at 02:36:12PM -0500, David P. Quigley wrote:
> > > > It looks like your patch is already in the tree as commit
> > > > 7c0ff870d1ed287504a61ed865f3d728c757436b. We saw this problem before and
> > > > Eric fixed it up. I thought it was very odd that you posted this 5
> > > > minutes ago and it was already upstream.
> > >
> > > Yeah, this has already been resolved, did that patch not solve the issue
> > > for you?
> >
> > I don't see how it couldn't have. The patch he submitted which he says
> > fixes the problem is the exact same patch that Eric submitted back in
> > Feb. Its possible that he is using a version of 2.6.33-rc8 that is based
> > off of a commit before the patch was merged since 2.6.33-rc8 was tagged
> > on Feb 12th and your commit date in the repo is Feb 16th.
>
> Yes, that is correct, I was only looking up to 2.6.33-rc8, I didn't
> think to check Linus's head branch, my mistake. It looks to me like
> the changeset you pointed to was put in Linus's tree after that tag,
> so it is fixed, just not in any tagged kernel.

2.6.33 is tagged, as is 2.6.34-rc1, so it should be showing up on your
end by now :)

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 |  Next  |  Last
Pages: 1 2
Prev: how to tweak ARP timer on kernel 2.6.9
Next: Staging: comedi:fix missing KERN_facility level in ni_labpc.c