public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stefan Liebler <stli@linux.ibm.com>
To: Iain Buclaw <ibuclaw@gdcproject.org>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] S/390: Fix PR91628
Date: Tue, 7 Apr 2020 16:33:01 +0200	[thread overview]
Message-ID: <df9f6b19-2b30-0997-f1c0-4d70d4a300f0@linux.ibm.com> (raw)
In-Reply-To: <8c0973a2-58c6-fb2b-9511-406047001639@linux.ibm.com>

On 4/1/20 6:20 PM, Stefan Liebler wrote:
> On 4/1/20 12:50 PM, Iain Buclaw wrote:
>>
>>
>> On 01/04/2020 08:28, Stefan Liebler wrote:
>>> ping
>>>
>>
>> Hi Stefan,
>>
>> As I've already said, I think that the name should be 
>> __ibmz_get_tls_offset to make clear that it is an internal function.
>>
>> Other than that, looks good to me.
>>
>> Iain.
>>
> 
> Hi Iain,
> 
> Sorry. I've missed your comment in the bugzilla.
> I've updated the name to __ibmz_get_this_offset.
> Nothing else is changed in the attached patch.
> 
> Please commit the patch upstream.
> Do you also close the bugzilla as soon as committed?
> 
> Regarding the mentioned musl-patch in your bugzilla comment:
> Yes, the diff looks like not conflicting.
> 
> Thanks,
> Stefan

Hi Iain,

Andreas has just committed the other patch "S/390: Fix layout of struct 
sigaction_t" to gcc after your pull-request was merged 
(https://github.com/dlang/druntime/pull/3020).

To me it seems that this patch is not simply pull-request-able to 
https://github.com/dlang/druntime.
As you've already mentioned "Other than that, looks good to me.", is 
this gcc patch okay to commit from your side? Then Andreas can also 
commit it and we can close the bugzilla.

Bye,
Stefan


  reply	other threads:[~2020-04-07 14:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 17:04 Stefan Liebler
2020-04-01  6:28 ` Stefan Liebler
2020-04-01 10:50   ` Iain Buclaw
2020-04-01 16:20     ` Stefan Liebler
2020-04-07 14:33       ` Stefan Liebler [this message]
2020-04-07 16:26         ` Iain Buclaw
2020-04-07 19:09           ` Andreas Krebbel

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=df9f6b19-2b30-0997-f1c0-4d70d4a300f0@linux.ibm.com \
    --to=stli@linux.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ibuclaw@gdcproject.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).