Skip to contentSkip to conversation

Bug 14594: fix for 2.6.31.8 ?

DISCUSSION Frank Schaefer 2 participants 5 messages Dec 14, 2009 – Dec 16, 2009

lore
Share & tools
lore
#0 lore raw

Bug 14594 has been fixed with commit e29d4363174949a7a4e46f670993d7ff43342c1c for 2.6.32 a month ago, but 2.6.28 - 2.6.31.7 are still affected.
Any plans to apply this at least for 2.6.31.8, too ?

Regards,
Frank Schaefer

#1 lore raw
Quoted 4 lines · Frank Schaefer

Bug 14594 has been fixed with commit e29d4363174949a7a4e46f670993d7ff43342c1c for 2.6.32 a month ago, but 2.6.28 - 2.6.31.7 are still affected.
Any plans to apply this at least for 2.6.31.8, too ?

It was never sent to the [email protected] alias so how would I know to apply this?

I'll queue it up for the next round.

thanks,

greg k-h

#2 lore raw
Quoted 11 lines · Greg KH
Quoted 5 lines · Frank Schaefer

Bug 14594 has been fixed with commit e29d4363174949a7a4e46f670993d7ff43342c1c for 2.6.32 a month ago, but 2.6.28 - 2.6.31.7 are still affected.
Any plans to apply this at least for 2.6.31.8, too ?

It was never sent to the [email protected] alias so how would I know to apply this?

I suspected that... no problem.
Btw, am I the one who is supposed to close this bug, too ? ;)

Quoted 6 lines

I'll queue it up for the next round.

thanks,

greg k-h

Thanks,
Frank Schaefer

#3 lore raw
Quoted 9 lines · Frank Schaefer
Quoted 8 lines · Greg KH
Quoted 5 lines · Frank Schaefer

Bug 14594 has been fixed with commit e29d4363174949a7a4e46f670993d7ff43342c1c for 2.6.32 a month ago, but 2.6.28 - 2.6.31.7 are still affected.
Any plans to apply this at least for 2.6.31.8, too ?

Quoted 5 lines
Quoted 3 lines

It was never sent to the [email protected] alias so how would I know to apply this?

I suspected that... no problem.
Btw, am I the one who is supposed to close this bug, too ? ;)

I have no idea, the owner should.

greg k-h

#4 lore raw
In reply to Frank Schaefer
Quoted 4 lines · Frank Schaefer

Bug 14594 has been fixed with commit e29d4363174949a7a4e46f670993d7ff43342c1c for 2.6.32 a month ago, but 2.6.28 - 2.6.31.7 are still affected.
Any plans to apply this at least for 2.6.31.8, too ?

Now queued up.

thanks,

greg k-h