Re: [ANNOUNCE] v4.9.30-rt20

2017-05-27 Thread Bernhard Landauer
Thanks a lot as always! I have a question regarding packager keys: It seems this time the patch has been signed with a different key than usual: unknown public key 4FE5E3262872E4CC Could you please let me know where you packager keys can be looked up? Thanks regards Bernhard On 27/05/17 18:

Re: [ANNOUNCE] v4.9.30-rt20

2017-05-27 Thread Bernhard Landauer
Yes, meanwhile I have looked it up and found that it belongs to 7B96E8162A8CF5D1 Sorry. All good! On 27/05/17 19:33, Sebastian Andrzej Siewior wrote: On 2017-05-27 19:19:51 [+0200], Bernhard Landauer wrote: Thanks a lot as always! I have a question regarding packager keys: It seems this time

Re: [ANNOUNCE] v4.9.30-rt20

2017-05-27 Thread Sebastian Andrzej Siewior
On 2017-05-27 19:19:51 [+0200], Bernhard Landauer wrote: > Thanks a lot as always! > I have a question regarding packager keys: > It seems this time the patch has been signed with a different key than > usual: > > unknown public key 4FE5E3262872E4CC > > Could you please let me know where you pack

[ANNOUNCE] v4.9.30-rt20

2017-05-27 Thread Sebastian Andrzej Siewior
Dear RT folks! I'm pleased to announce the v4.9.30-rt20 patch set. Changes since v4.9.30-rt19: - The patch "timers: Don't wake ktimersoftd on every tick" has been reverted because this optimisation can lead to timers not getting expired. Reported by Klaus Gusenleitner, debugged by Ann