From: Bob Tracy <rct@gherkin.frus.com>
To: linux-alpha@vger.kernel.org, debian-alpha@lists.debian.org
Cc: mcree@orcon.net.nz, mattst88@gmail.com
Subject: [PATCH] 4.18-rc7 on alpha: bitsperlong issue
Date: Mon, 21 Jan 2019 15:42:32 -0600 [thread overview]
Message-ID: <20190121214232.GA14964@gherkin.frus.com> (raw)
In-Reply-To: <20190121161928.GA12984@gherkin.frus.com>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
Apologies for what is essentially a repost with a proper subject header
in the sense of trying to get the attention of people who collect/approve
patches for submission upstream. See my posting from earlier today
(followup: [FTBFS] kernel 4.18-rc7 bitsperlong.h issue on alpha) for the
back story. As mentioned there, this patch applies cleanly to at least
all mainline kernel source trees >= version 4.18.
Further apologies for including the patch as an attachment, but I don't
trust my mailer not to impose unintended formatting.
--Bob
Signed-off-by: Bob Tracy <rct@frus.com>
Tested-by: Bob Tracy <rct@frus.com>
[-- Attachment #2: patch18_bitsperlong --]
[-- Type: text/plain, Size: 458 bytes --]
--- a/tools/include/uapi/asm/bitsperlong.h 2019-01-20 14:40:32.522422998 -0600
+++ b/tools/include/uapi/asm/bitsperlong.h 2019-01-21 09:51:45.336938260 -0600
@@ -13,6 +13,8 @@
#include "../../arch/mips/include/uapi/asm/bitsperlong.h"
#elif defined(__ia64__)
#include "../../arch/ia64/include/uapi/asm/bitsperlong.h"
+#elif defined(__alpha__)
+#include "../../arch/alpha/include/uapi/asm/bitsperlong.h"
#else
#include <asm-generic/bitsperlong.h>
#endif
next prev parent reply other threads:[~2019-01-21 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 16:19 followup: [FTBFS] kernel 4.18-rc7 bitsperlong.h issue on alpha Bob Tracy
2019-01-21 21:42 ` Bob Tracy [this message]
2019-01-22 7:35 ` [PATCH] 4.18-rc7 on alpha: bitsperlong issue Matt Turner
2019-01-22 9:21 ` Philippe Mathieu-Daudé
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=20190121214232.GA14964@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=linux-alpha@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
/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