From: john stultz <johnstul@us.ibm.com>
To: James Cloos <cloos@jhcloos.com>
Cc: davehart_gmail_exchange_tee@davehart.net, hackers@lists.ntp.org,
linux-kernel@vger.kernel.org,
Roman Zippel <zippel@linux-m68k.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [ntp:hackers] ntp-dev-4.2.5p235-RC build failure: MOD_NANO not #defined
Date: Tue, 20 Oct 2009 17:43:58 -0700 [thread overview]
Message-ID: <1256085838.3346.45.camel@localhost> (raw)
In-Reply-To: <m3aazlk5vz.fsf@lugabout.jhcloos.org>
On Tue, 2009-10-20 at 19:22 -0400, James Cloos wrote:
> >>>>> "john" == john stultz <johnstul@us.ibm.com> writes:
>
> john> The kernel has already been fixed, but glibc still needs to pick up the change.
> john> See the kernel commit here:
> john> http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=commitdiff;h=c95b4502ad7fe8f3b9954aec794b00ac0046ab3a
>
> Ah. I only looked in my (up to date) clone of Linus’ tree; I didn’t
> check the trees-to-pull.
Huh. I guess I was mistaken and had mixed up my bookmarks. You're right,
I thought it was already upstream, but I've been looking at the wrong
tree. The patch is not yet in mainline.
> Will that be part of a pull request for the current rc or only for the
> next merge window?
Ingo, any eta on when commit c95b4502ad7fe8f3b9954aec794b00ac0046ab3a
will be pushed? Not sure how it got missed this last cycle.
thanks
-john
next prev parent reply other threads:[~2009-10-21 0:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 18:38 ntp-dev-4.2.5p235-RC build failure: MOD_NANO not #defined James Cloos
2009-10-20 19:27 ` [ntp:hackers] " Dave Hart
2009-10-20 20:45 ` john stultz
2009-10-20 23:22 ` James Cloos
2009-10-21 0:43 ` john stultz [this message]
2009-10-21 23:03 ` Reg Clemens
2009-10-22 1:58 ` Harlan Stenn
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=1256085838.3346.45.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=cloos@jhcloos.com \
--cc=davehart_gmail_exchange_tee@davehart.net \
--cc=hackers@lists.ntp.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox