From: "J. Johnston" <jjohnstn@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: David Carlton <carlton@kealia.com>, gdb <gdb@sources.redhat.com>,
Elena Zannoni <ezannoni@redhat.com>,
msnyder@redhat.com
Subject: Re: status of NTPL patches
Date: Fri, 27 Jun 2003 17:52:00 -0000 [thread overview]
Message-ID: <3EFC83BF.3070508@redhat.com> (raw)
In-Reply-To: <20030627162358.GA29641@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Fri, Jun 27, 2003 at 12:17:20PM -0400, J. Johnston wrote:
>
>>Daniel Jacobowitz wrote:
>>
>>>On Fri, Jun 27, 2003 at 08:48:04AM -0700, David Carlton wrote:
>>>
>>>
>>>>What's the status of the NTPL patches? Are they all in mainline yet?
>>>>I'm about to sync my branch with mainline, and I'm curious if I'm
>>>>allowed to tell my local users that it's okay to use it with Red Hat
>>>>9.0 yet.
>>>
>>>
>>>I believe that it should work.
>>>
>>
>>They are all committed except for Michael's rewrite of the gcore patch
>>which I haven't
>>seen a commit notice for yet. I don't see any reason it can't be checked
>>in - Michael?
>
>
> Do you mean:
> 2003-06-19 Michael Snyder <msnyder@redhat.com>
>
> * linux-nat.h: New file.
> * linux-nat.c: Include linux-nat.h.
> * lin-lwp.c: Include linux-nat.h.
> Move struct lwp_info def to linux-nat.h.
> * linux-proc.c: Include linux-nat.h.
> (linux_make_note_section): Iterate over lwps instead of threads.
> (linux_do_thread_registers): Use lwp instead of merged pid.
> * config/nm-linux.h: Move miscelaneous def'ns to linux-nat.h.
> * Makefile.in (lin-lwp.o, linux-proc.o, linux-nat.o):
> Add dependency on linux_nat_h.
>
> ?
>
Yes. Didn't see a post about it being committed. Thanks.
-- Jeff J.
prev parent reply other threads:[~2003-06-27 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 15:52 David Carlton
2003-06-27 16:17 ` Daniel Jacobowitz
2003-06-27 16:24 ` J. Johnston
2003-06-27 16:36 ` Daniel Jacobowitz
2003-06-27 17:49 ` Elena Zannoni
2003-06-27 17:52 ` J. Johnston [this message]
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=3EFC83BF.3070508@redhat.com \
--to=jjohnstn@redhat.com \
--cc=carlton@kealia.com \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).