Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@mips.com>
To: Djordje Todorovic <djordje.todorovic@rt-rk.com>,
	Pedro Alves	<palves@redhat.com>
Cc: <binutils@sourceware.org>, <gdb-patches@sourceware.org>,
	"nemanja.popov@rt-rk.com" <nemanja.popov@rt-rk.com>,
	<petar.jovanovic@rt-rk.com>,
	"Ananthakrishna Sowda (asowda)"	<asowda@cisco.com>,
	Nikola Prica <nikola.prica@rt-rk.com>
Subject: Re: [PATCH 0/3] Fix issues with writing Linux core PRSTATUS note on MIPS o32, n32 and n64 into core file
Date: Tue, 07 Nov 2017 21:59:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1711072131070.10088@tp.orcam.me.uk> (raw)
In-Reply-To: <8475f0b7-969d-3c27-27f2-a4944e58e954@rt-rk.com>

Hi Djordje,

> >Can you please use the time to enter the bug report, and 
> >can you also tell me if your copyright assignment has been sorted out with 
> >FSF?
> 
> The bug report is created and it can be found on the following link:
> https://sourceware.org/bugzilla/show_bug.cgi?id=22381

 Thank you, I have updated it with some pointers, based on your earlier 
reference.

> Also, the copyright assignment with FSF has been sorted out.

 Great!

> >    if {![string match $host_triplet $target_triplet]} {
> >	setup_kfail "gdb/..." "*-*-*"
> >    }
> >
> >really (`isnative' doesn't help here as it's too restrictive: we could 
> >have a native GDB built on a different system; this is actually what I use 
> >as I don't currently have an adequate version of native MIPS GCC set up).
> 
> I agree with you that this is more appropriate way to do it.
> 
> So, could you please, tell me do you want from me to resubmit the whole patch series
> or just the last one?

 I think there is no point in resending, as long as Pedro is fine with 
and approves your most recent version of the test case patch posted (NB 
it helps if on resubmission you number patch revisions in the subject 
line like [PATCH v3 2/3]).  Pedro?

 Once we've got the final ack from Pedro, I'll proceed with the right 
steps to push your changes, with the tweaks noted in the final review 
round applied.  I'll post the actual patches committed, for posterity.

  Maciej


  reply	other threads:[~2017-11-07 21:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 13:47 Djordje Todorovic
2017-10-17 13:55 ` Maciej W. Rozycki
2017-10-17 13:57   ` Djordje Todorovic
2017-10-25 14:15   ` Djordje Todorovic
2017-10-25 22:40     ` Maciej W. Rozycki
2017-10-26 11:22       ` Djordje Todorovic
2017-10-30 13:44         ` Maciej W. Rozycki
2017-10-30 14:12           ` Maciej W. Rozycki
2017-11-03 13:05             ` Djordje Todorovic
2017-11-07 21:59               ` Maciej W. Rozycki [this message]
2017-11-08 10:10                 ` Pedro Alves
2017-11-08 21:23                   ` Maciej W. Rozycki
2017-11-08 21:24                     ` [committed v7 2/3] BFD: Extract PID from MIPS core dump file Maciej W. Rozycki
2017-11-08 21:24                     ` [committed v7 1/3] BFD: Write Linux core PRSTATUS note into MIPS core file Maciej W. Rozycki
2017-11-08 21:26                     ` [committed v7 3/3] Add test for fetching TLS from " Maciej W. Rozycki
2017-11-09 10:32                 ` [PATCH 0/3] Fix issues with writing Linux core PRSTATUS note on MIPS o32, n32 and n64 into " Djordje Todorovic
2017-11-09 22:41                   ` Maciej W. Rozycki
2017-11-07 21:31           ` Maciej W. Rozycki
2017-11-08  9:56             ` Pedro Alves
2017-11-08 18:41               ` Maciej W. Rozycki
2017-10-27 15:00       ` Pedro Alves
2017-10-30 13:38         ` Maciej W. Rozycki

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.1711072131070.10088@tp.orcam.me.uk \
    --to=macro@mips.com \
    --cc=asowda@cisco.com \
    --cc=binutils@sourceware.org \
    --cc=djordje.todorovic@rt-rk.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nemanja.popov@rt-rk.com \
    --cc=nikola.prica@rt-rk.com \
    --cc=palves@redhat.com \
    --cc=petar.jovanovic@rt-rk.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