From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH] Handle MIPS Linux SIGTRAP siginfo.si_code values
Date: Wed, 24 Feb 2016 20:49:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1602242040130.15885@tp.orcam.me.uk> (raw)
In-Reply-To: <56CDFE38.1000604@codesourcery.com>
On Wed, 24 Feb 2016, Luis Machado wrote:
> I think we should converge to a standard solution across all architectures in
> the future rather than potentially perpetuate old non-standard ways. So the
> movement towards returning well defined si_code values in the MIPS Linux
> Kernel is a plus, even though we might not benefit from it right now. I'm in
> favor of having the change to the kernel made.
Not right now as in: "not earlier than in 2-3 months' time needed for a
proper kernel release", which is when 4.6.0 is likely to happen? Well, I
think it's not much waiting really unless you don't care, in which case
you'll get it with your next regular kernel upgrade scheduled.
Maciej
next prev parent reply other threads:[~2016-02-24 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 16:44 Pedro Alves
2016-02-24 18:29 ` Maciej W. Rozycki
2016-02-24 18:51 ` Pedro Alves
2016-02-24 19:02 ` Luis Machado
2016-02-24 20:49 ` Maciej W. Rozycki [this message]
2016-02-24 21:10 ` Luis Machado
2016-02-24 20:39 ` Maciej W. Rozycki
2016-02-24 23:20 ` Pedro Alves
2016-02-24 23:37 ` [PATCH] MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT Pedro Alves
2016-02-25 1:39 ` [PATCH] Handle MIPS Linux SIGTRAP siginfo.si_code values Maciej W. Rozycki
2016-02-25 1:45 ` Pedro Alves
2016-04-05 16:57 ` Maciej W. Rozycki
2016-04-15 23:17 ` Pedro Alves
2016-02-24 18:51 ` Luis Machado
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=alpine.DEB.2.00.1602242040130.15885@tp.orcam.me.uk \
--to=macro@imgtec.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=macro@linux-mips.org \
--cc=palves@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).