public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: cmetcalf@tilera.com
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH] tile: fix DWARF bug in clone() for created thread
Date: Fri, 21 Dec 2012 20:21:00 -0000	[thread overview]
Message-ID: <20121221.122051.288743555054863562.davem@davemloft.net> (raw)
In-Reply-To: <50D4C30D.1020803@tilera.com>

From: Chris Metcalf <cmetcalf@tilera.com>
Date: Fri, 21 Dec 2012 15:14:05 -0500

> On 12/14/2012 10:46 AM, Chris Metcalf wrote:
>>   [David - this is pretty low risk (just adds one DWARF CFI directive),
>>   but also fixes a pretty minor bug.  So your call as to whether I should
>>   wait for 2.18 to commit.]
> 
> Ping?  I like the idea of fixing this in 2.17 just because customers
> tend to go "WTF?" when they see this in the debugger output.

Ok.

      reply	other threads:[~2012-12-21 20:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14 15:52 Chris Metcalf
2012-12-21 20:14 ` Chris Metcalf
2012-12-21 20:21   ` 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=20121221.122051.288743555054863562.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=cmetcalf@tilera.com \
    --cc=libc-ports@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).