From: Borislav Petkov <bp@alien8.de>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Joe Perches <joe@perches.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/uaccess: Remove unused __addr_ok() macro
Date: Wed, 27 Mar 2019 14:15:36 +0100 [thread overview]
Message-ID: <20190327131536.GF32571@zn.tnic> (raw)
In-Reply-To: <alpine.DEB.2.21.999.1903032242440.4505@trent.utfs.org>
On Sun, Mar 03, 2019 at 10:47:00PM -0800, Christian Kujau wrote:
> If so, would simly removing it do the trick or is there more magic
> involved? I don't have that many cross-compilers though and it's not even
> build-tested:
There are cross compilers here:
https://www.kernel.org/pub/tools/crosstool/
which you can use.
And perhaps splitting that patch per architecture and letting arch
maintainers apply each, would be easier. I think.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-03-27 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 19:11 [PATCH] x86/uaccess: Remove unused __addr_ok() macro Borislav Petkov
2019-02-25 19:20 ` Linus Torvalds
2019-02-25 19:42 ` Borislav Petkov
2019-02-25 21:08 ` Joe Perches
2019-03-04 6:47 ` Christian Kujau
2019-03-27 13:15 ` Borislav Petkov [this message]
2019-02-25 22:43 ` [tip:x86/cleanups] " tip-bot for Borislav Petkov
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=20190327131536.GF32571@zn.tnic \
--to=bp@alien8.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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