All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-sh@vger.kernel.org
Subject: Re: Build fails with unknown symbol __get_user_unknown with InifiniBand enabled
Date: Fri, 29 May 2020 11:21:26 +0000	[thread overview]
Message-ID: <CAMuHMdV2F-RqeG7ZgO3jJy+_JobkCnYnZ_PWm__dtPRKQY2gVQ@mail.gmail.com> (raw)
In-Reply-To: <8945f9b7-d4d3-851e-dc4f-2d05ed94c169@physik.fu-berlin.de>

Hi Adrian,

On Fri, May 29, 2020 at 12:35 PM John Paul Adrian Glaubitz
<glaubitz@physik.fu-berlin.de> wrote:
> On 5/29/20 12:21 PM, Geert Uytterhoeven wrote:
> >> Would this be fixed by Arnds patch series to remove SH-5 support by any chance?
> >
> > No, it won't. As this is uaccess_32.h, i.e. for sh32.
> > All architectures are supposed to implement 64-bit get_user() accesses.
>
> Ok, I assume we need an implementation like this then [1]?
>
> Adrian
>
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id²f680380ddf2f003882e59e00acd6c1952f91fc

Exactly.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      parent reply	other threads:[~2020-05-29 11:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29  9:03 Build fails with unknown symbol __get_user_unknown with InifiniBand enabled John Paul Adrian Glaubitz
2020-05-29  9:59 ` Geert Uytterhoeven
2020-05-29 10:12 ` John Paul Adrian Glaubitz
2020-05-29 10:21 ` Geert Uytterhoeven
2020-05-29 10:35 ` John Paul Adrian Glaubitz
2020-05-29 11:21 ` Geert Uytterhoeven [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=CAMuHMdV2F-RqeG7ZgO3jJy+_JobkCnYnZ_PWm__dtPRKQY2gVQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-sh@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 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.