From: Alan Mackenzie <acm@muc.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
34235@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Alex Branham <alex.branham@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 (posix-timers: Fix division by zero bug). Problems with glibc.
Date: Tue, 5 Feb 2019 13:54:23 +0000 [thread overview]
Message-ID: <20190205135423.GA3919@ACM> (raw)
In-Reply-To: <alpine.DEB.2.21.1902041724200.3006@nanos.tec.linutronix.de>
Hello, Thomas.
On Mon, Feb 04, 2019 at 17:25:11 +0000, Thomas Gleixner wrote:
> On Sat, 2 Feb 2019, Alan Mackenzie wrote:
[ .... ]
> > I've just built and installed Linux 4.19.19, and it does indeed solve
> > the Emacs profiler bug, #34235. :-)
> > I see that the patch has been installed in 4.20.6, 4.19.19, and 4.14.97.
> > Are there any plans to install it into 4.9.x, the other live long term
> > support branch? The reason I ask is to make an entry into Emacs's
> > PROBLEMS file, telling users and distributions which kernel versions to
> > upgrade to.
> 4.9 doesn't have the offending commit AFAICT.
OK, thanks very much! I've put these three version numbers into the
message in Emacs's PROBLEMS file.
I think we're finished, now.
> Thanks,
> tglx
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-02-05 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 21:47 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 (posix-timers: Fix division by zero bug). Problems with glibc Alan Mackenzie
2019-02-01 22:04 ` Thomas Gleixner
2019-02-02 10:44 ` Alan Mackenzie
2019-02-04 17:25 ` Thomas Gleixner
2019-02-05 13:54 ` Alan Mackenzie [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-02 2:07 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 (posix-timers: Fix, " Paul Eggert
2019-02-02 9:21 ` Thomas Gleixner
2019-02-03 6:28 ` Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190205135423.GA3919@ACM \
--to=acm@muc.de \
--cc=34235@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.