----- Original Message ----- > From: "David Woodhouse" <david.woodho...@intel.com> > To: "CAI Qian" <caiq...@redhat.com> > Cc: stable@vger.kernel.org, "David Miller" <da...@davemloft.net>, "Jason > Wang" <jasow...@redhat.com> > Sent: Monday, January 14, 2013 6:24:37 PM > Subject: Re: [PATCH 3.7.x] 8139cp: set ring address after enabling C+ mode > > On Mon, 2013-01-14 at 03:20 -0500, CAI Qian wrote: > > This is a backport patch that adjusted the context in order to be > > applied on the 3.7.x stable. Feel free to ACK/NAK it. > > Looks incredibly similar to what we have at > http://git.infradead.org/users/dwmw2/openwrt.git/blob/HEAD:/target/linux/generic/patches-3.7/065-8139cp-fixes.patch > > So if you want to do it that way, it should work. > > However, I thought the plan for 3.7 was just to revert the offending > commit (b01af457) which introduced the problem. That's already been > done, which is why the patch in $SUBJECT failed to apply, right? Hmm David, a bit confused here. b01af457 (the offender) was merged in v3.5-rc1. b26623da (the revert) was merged in v3.7-rc7. a9dbe40f (this commit marked for stable) was merged in v3.8-rc1.
Now, we want to back-port a9dbe40f to the 3.7.x stable series (since it has been marked for stable) which my patch was about since a9dbe40f can't be applied as it is seems due to context differ between 3.8 and 3.7 code-base. Am I missing anything? Regards, CAI Qian > > Reverting the original commit will have re-introduced the bug it > intended to fix, but I don't think we were ever sure that it had > really > triggered in practice anyway? Jason? > > -- > Sent with MeeGo's ActiveSync support. > > David Woodhouse Open Source Technology > Centre > david.woodho...@intel.com Intel > Corporation > > > > -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
