From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Ungerer <gerg@uclinux.org>, Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH v2] m68k: use conventional function parameters for do_sigreturn
Date: Thu, 25 Feb 2016 11:55:23 +0100 [thread overview]
Message-ID: <mvmy4a9t5yc.fsf@hawking.suse.de> (raw)
In-Reply-To: <CAMuHMdVPsqEYwgoXrS6ecdPBUEvDqhaCBYNZPY7op02o70LonQ@mail.gmail.com> (Geert Uytterhoeven's message of "Thu, 25 Feb 2016 11:42:08 +0100")
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> Hi Greg,
>
> On Wed, Feb 24, 2016 at 2:10 AM, Greg Ungerer <gerg@uclinux.org> wrote:
>> Do you have any objections or issues with this change?
>>
>> Andreas and Philippe kindly gave feedback, which I have addressed
>> (I think to everyone's satisfaction?)
>>
>> I would very much like to see this applied to resolve the compilation
>> issue for non-MMU with modern versions of gcc. I don't mind pushing
>> through my tree. I just want to make sure first that nobody objects
>> to this change or has any remaining issues with it.
>
> If Andreas is happy with it, I will apply it.
No objections.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-02-25 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 6:36 [PATCH v2] m68k: use conventional function parameters for do_sigreturn Greg Ungerer
2016-02-15 10:03 ` Philippe De Muyter
2016-02-15 13:06 ` Greg Ungerer
2016-02-15 14:57 ` Philippe De Muyter
2016-02-24 1:10 ` Greg Ungerer
2016-02-25 10:42 ` Geert Uytterhoeven
2016-02-25 10:55 ` Andreas Schwab [this message]
2016-02-29 9:36 ` Geert Uytterhoeven
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=mvmy4a9t5yc.fsf@hawking.suse.de \
--to=schwab@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.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