From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Chen Liqin <liqin.linux@gmail.com>,
Lennox Wu <lennox.wu@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] module.h --> extable.h fixup for arch/score
Date: Sat, 11 Mar 2017 13:42:48 -0500 [thread overview]
Message-ID: <20170311184248.GQ7825@windriver.com> (raw)
Linus, please pull to get a small fixup for arch/score.
It seems that Guenter is the only one on the planet doing builds for
arch/score -- we don't have compile coverage for it in linux-next or in
the kbuild-bot either. Guenter couldn't even recall where he got his
toolchain, but was kind enough to share it with me so I could validate
this change and also add arch/score to my build coverage.
I sat on this a bit in case there was any other fallout in other arch
dirs, but since this still seems to be the only one, I might as well
send it on its way.
Thanks,
Paul.
---
The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux.git tags/extable-fix
for you to fetch changes up to 0acf611997d9d05dbfb559c3c6e379c861eb5957:
score: Fix implicit includes now failing build after extable change (2017-03-11 11:57:21 -0500)
----------------------------------------------------------------
Fixup for arch/score after extable.h introduction
----------------------------------------------------------------
Guenter Roeck (1):
score: Fix implicit includes now failing build after extable change
arch/score/kernel/traps.c | 1 +
arch/score/mm/extable.c | 2 ++
2 files changed, 3 insertions(+)
reply other threads:[~2017-03-11 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170311184248.GQ7825@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=lennox.wu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=liqin.linux@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox