From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Russell King <linux@armlinux.org.uk>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/3] Remove checks for gcc < 4
Date: Wed, 14 Jul 2021 12:04:07 +0200 [thread overview]
Message-ID: <cover.1626256876.git.geert+renesas@glider.be> (raw)
Hi all,
This patch removes the few remaining checks for gcc < 4, which is no
longer supported for building the kernel.
All three patches can be applied independently.
Changes compared to v1:
- Add Acked-by,
- Drop applied patch.
Thanks!
Geert Uytterhoeven (3):
ARM: div64: Remove always-true __div64_const32_is_OK() duplicate
ARM: unified: Remove check for gcc < 4
asm-generic: div64: Remove always-true __div64_const32_is_OK()
arch/arm/include/asm/div64.h | 11 -----------
arch/arm/include/asm/unified.h | 4 ----
include/asm-generic/div64.h | 14 ++++----------
3 files changed, 4 insertions(+), 25 deletions(-)
--
2.25.1
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
next reply other threads:[~2021-07-14 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 10:04 Geert Uytterhoeven [this message]
2021-07-14 10:04 ` [PATCH v2 1/3] ARM: div64: Remove always-true __div64_const32_is_OK() duplicate Geert Uytterhoeven
2021-07-14 10:04 ` [PATCH v2 2/3] ARM: unified: Remove check for gcc < 4 Geert Uytterhoeven
2021-07-14 10:04 ` [PATCH v2 3/3] asm-generic: div64: Remove always-true __div64_const32_is_OK() 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=cover.1626256876.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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
all inboxes | Powered by JetHome®