From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v1 1/1] kernel.h: split out panic and oops helpers (ia64 fix)
Date: Fri, 21 May 2021 07:24:08 +0000 [thread overview]
Message-ID: <41bbace7-1b09-8464-a082-e4152f07fdb4@physik.fu-berlin.de> (raw)
In-Reply-To: <YKZhcKqomWxH3eph@smile.fi.intel.com>
Hi Andy!
On 5/20/21 3:17 PM, Andy Shevchenko wrote:
> On Thu, May 20, 2021 at 03:12:24PM +0200, John Paul Adrian Glaubitz wrote:
>> On 5/20/21 3:05 PM, Andy Shevchenko wrote:
>>> Note, this patch is untested. I have no ia64 compiler at hand.
>
>> I can test it later today.
>
> Appreciate it, thanks!
>
> This is against Linux Next (where Andrew's patches are sitting for a while).
I just pulled linux-next and was able to build a kernel for my RX-2600 without any
problems. Since your patch is already in the tree, I assume it's correct.
Do you want me to test anything else? I can test-boot the kernel later, but I want
to avoid that now since I don't want to turn on the noisy server while at home :-).
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2021-05-21 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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:17 ` Andy Shevchenko
2021-05-21 7:24 ` John Paul Adrian Glaubitz [this message]
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=41bbace7-1b09-8464-a082-e4152f07fdb4@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--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: 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