From: David Miller <davem@davemloft.net>
To: palves@redhat.com
Cc: gdb-patches@sourceware.org, stan@codesourcery.com, kcy@codesourcery.com
Subject: Re: [PATCH] Fix 'info os' crashes on sparc.
Date: Tue, 20 Nov 2012 17:41:00 -0000 [thread overview]
Message-ID: <20121120.124103.2030641947073178567.davem@davemloft.net> (raw)
In-Reply-To: <50AB9757.20204@redhat.com>
From: Pedro Alves <palves@redhat.com>
Date: Tue, 20 Nov 2012 14:44:39 +0000
> On 11/20/2012 06:13 AM, David Miller wrote:
>
>> gdb/
>>
>> 2012-11-19 David S. Miller <davem@davemloft.net>
>>
>> * common/linux-osdata.c (get_number_of_cpu_cores): Delete.
>> (linux_xfer_osdata_processes): Fetch _SC_NPROCESSORS_ONLN via
>> sysconf.
>> (get_cores_used_by_process): Update comment.
>
> OK. Thanks.
Thanks for reviewing, committed.
prev parent reply other threads:[~2012-11-20 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121120.003006.1287326526424655175.davem@davemloft.net>
2012-11-20 6:13 ` David Miller
2012-11-20 14:44 ` Pedro Alves
2012-11-20 17:41 ` David Miller [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=20121120.124103.2030641947073178567.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gdb-patches@sourceware.org \
--cc=kcy@codesourcery.com \
--cc=palves@redhat.com \
--cc=stan@codesourcery.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