From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> To: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Andrew Morton <akpm@linux-foundation.org>, Andy Shevchenko <andriy.shevchenko@linux.intel.com>, kernel test robot <lkp@intel.com> Subject: [PATCH v1 1/1] kernel.h: split out panic and oops helpers (ia64 fix) Date: Thu, 20 May 2021 16:05:57 +0300 [thread overview] Message-ID: <20210520130557.55277-1-andriy.shevchenko@linux.intel.com> (raw) Follow up fix for the "kernel.h: split out panic and oops helpers" patch. Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> --- Andrew, please add as a fix to the above mentioned patch, thanks! For the record, I haven't got any other messages from any of CIs/bots, presumably there will be no more or very little reports. Note, this patch is untested. I have no ia64 compiler at hand. arch/ia64/include/asm/pal.h | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/ia64/include/asm/pal.h b/arch/ia64/include/asm/pal.h index 5c51fceedaf9..e6b652f9e45e 100644 --- a/arch/ia64/include/asm/pal.h +++ b/arch/ia64/include/asm/pal.h @@ -99,6 +99,7 @@ #include <linux/types.h> #include <asm/fpu.h> +#include <asm/intrinsics.h> /* * Data types needed to pass information into PAL procedures and -- 2.30.2
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> To: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Andrew Morton <akpm@linux-foundation.org>, Andy Shevchenko <andriy.shevchenko@linux.intel.com>, kernel test robot <lkp@intel.com> Subject: [PATCH v1 1/1] kernel.h: split out panic and oops helpers (ia64 fix) Date: Thu, 20 May 2021 13:05:57 +0000 [thread overview] Message-ID: <20210520130557.55277-1-andriy.shevchenko@linux.intel.com> (raw) Follow up fix for the "kernel.h: split out panic and oops helpers" patch. Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> --- Andrew, please add as a fix to the above mentioned patch, thanks! For the record, I haven't got any other messages from any of CIs/bots, presumably there will be no more or very little reports. Note, this patch is untested. I have no ia64 compiler at hand. arch/ia64/include/asm/pal.h | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/ia64/include/asm/pal.h b/arch/ia64/include/asm/pal.h index 5c51fceedaf9..e6b652f9e45e 100644 --- a/arch/ia64/include/asm/pal.h +++ b/arch/ia64/include/asm/pal.h @@ -99,6 +99,7 @@ #include <linux/types.h> #include <asm/fpu.h> +#include <asm/intrinsics.h> /* * Data types needed to pass information into PAL procedures and -- 2.30.2
next reply other threads:[~2021-05-20 13:05 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-20 13:05 Andy Shevchenko [this message] 2021-05-20 13:05 ` [PATCH v1 1/1] kernel.h: split out panic and oops helpers (ia64 fix) Andy Shevchenko 2021-05-20 13:12 ` John Paul Adrian Glaubitz 2021-05-20 13:12 ` John Paul Adrian Glaubitz 2021-05-20 13:17 ` Andy Shevchenko 2021-05-20 13:17 ` Andy Shevchenko 2021-05-21 7:24 ` John Paul Adrian Glaubitz 2021-05-21 7:24 ` John Paul Adrian Glaubitz 2021-05-21 12:02 ` Andy Shevchenko 2021-05-21 12:02 ` Andy Shevchenko
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=20210520130557.55277-1-andriy.shevchenko@linux.intel.com \ --to=andriy.shevchenko@linux.intel.com \ --cc=akpm@linux-foundation.org \ --cc=linux-ia64@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lkp@intel.com \ /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: linkBe 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.