From: Helge Deller <deller@gmx.de>
To: Miklos Szeredi <miklos@szeredi.hu>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Parisc List <linux-parisc@vger.kernel.org>,
"James E.J. Bottomley" <jejb@parisc-linux.org>
Subject: Re: Linux 3.15-rc6
Date: Fri, 23 May 2014 11:16:56 +0200 [thread overview]
Message-ID: <537F1208.8090800@gmx.de> (raw)
In-Reply-To: <CAJfpeguNGFDw_7C1JgZv3Wjgd0ku9QhEkUy_+gprOS58sBXaSQ@mail.gmail.com>
On 05/23/2014 11:12 AM, Miklos Szeredi wrote:
> On Fri, May 23, 2014 at 3:27 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>> On Thu, May 22, 2014 at 6:07 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>>> On 05/22/2014 05:43 PM, Linus Torvalds wrote:
>>>>
>>>>
>>>> only s390 seems to need a compat wrapper, and s390 is kind of odd in
>>>> many respects, so I suspect renameat2 should just use ENTRY_SAME() on
>>>> parisc, but without any way to *test* it I won't apply the patch.
>>>>
>>>> Guenter, I assume that changing the
>>>>
>>>> ENTRY_COMP(renameat2)
>>>>
>>>> line in arch/parisc/kernel/syscall_table.S to use ENTRY_SAME() at
>>>> least fixes the compile error?
>>>
>>> Yes, it fixes the build error for parisc64, and parisc (32 bit) still
>>> builds.
>>
>> Ok. I'd like to get some kind of confirmation that it is expected to
>> work too. Miklos/Helge?
>
> Oops, yes, it should be ENTRY_SAME().
Yes, ENTRY_SAME() is correct. Sorry, it was my fault that I didn't noticed earlier.
Helge
prev parent reply other threads:[~2014-05-23 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 22:47 Linux 3.15-rc6 Linus Torvalds
2014-05-22 17:20 ` Guenter Roeck
2014-05-23 0:43 ` Linus Torvalds
2014-05-23 1:07 ` Guenter Roeck
2014-05-23 1:27 ` Linus Torvalds
2014-05-23 9:12 ` Miklos Szeredi
2014-05-23 9:16 ` Helge Deller [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=537F1208.8090800@gmx.de \
--to=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.