Prev: Staging: rtl8192e/ieee80211: remove kernel version compatibility wrappers
Next: Staging: memrar: Moved memrar_allocator struct into memrar_allocator.c
From: Rafael J. Wysocki on 22 Jun 2010 18:00 On Tuesday, June 22, 2010, Paul E. McKenney wrote: > On Mon, Jun 21, 2010 at 12:34:25AM +0200, Rafael J. Wysocki wrote: > > This message has been generated automatically as a part of a report > > of regressions introduced between 2.6.33 and 2.6.34. > > > > The following bug entry is on the current list of known regressions > > introduced between 2.6.33 and 2.6.34. Please verify if it still should > > be listed and let the tracking team know (either way). > > We have been knocking these off as they appear. There is one or two > that the relevant maintainers have been ignoring, but that always seems > to be the case. ;-) > > Your choice as to whether you want to track the group... I think I'll simply leave that one bug open until all known instances have been dealt with. Please let me know when that happens. :-) Thanks, Rafael -- 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: Rafael J. Wysocki on 22 Jun 2010 20:20
On Wednesday, June 23, 2010, Paul E. McKenney wrote: > On Tue, Jun 22, 2010 at 11:49:12PM +0200, Rafael J. Wysocki wrote: > > On Tuesday, June 22, 2010, Paul E. McKenney wrote: > > > On Mon, Jun 21, 2010 at 12:34:25AM +0200, Rafael J. Wysocki wrote: > > > > This message has been generated automatically as a part of a report > > > > of regressions introduced between 2.6.33 and 2.6.34. > > > > > > > > The following bug entry is on the current list of known regressions > > > > introduced between 2.6.33 and 2.6.34. Please verify if it still should > > > > be listed and let the tracking team know (either way). > > > > > > We have been knocking these off as they appear. There is one or two > > > that the relevant maintainers have been ignoring, but that always seems > > > to be the case. ;-) > > > > > > Your choice as to whether you want to track the group... > > > > I think I'll simply leave that one bug open until all known instances have been > > dealt with. > > > > Please let me know when that happens. :-) > > So if I am sufficiently forgetful, I can just ask you to close the > bug immediately? > > Sorry, but you really couldn't expect me to pass up that kind of > loophole! ;-) OK, closed. Thanks, Rafael -- 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/ |