linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qian Cai <quic_qiancai@quicinc.com>
To: Bing Fan <hptsfb@gmail.com>, <gregkh@linuxfoundation.org>,
	Bing Fan <tombinfan@tencent.com>
Cc: <linux-serial@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5] arm pl011 serial: support multi-irq request
Date: Mon, 26 Jul 2021 12:39:24 -0400	[thread overview]
Message-ID: <a1843494-5c8e-1ec8-5b98-df318db40922@quicinc.com> (raw)
In-Reply-To: <3b60d054-4e22-62fa-c31b-29b146495a65@gmail.com>



On 7/26/2021 3:17 AM, Bing Fan wrote:
> Hello,
> 
> I tried to reproduce, but unfortunately, it didn't, and the dmesg log as
> attachment.
> 
> I had enabled CONFIG_KASAN and CONFIG_SLUB_DEBUG_ON configs.
> 
> Can you describe the flow of your operation?
> 
Nothing fancy. Just boot a baremetal ARM server on linux-next could trigger it.
The .config is here.

https://www.lsbug.org/tmp/arm64.conf

  reply	other threads:[~2021-07-26 16:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01  1:38 [PATCH v5] arm pl011 serial: support multi-irq request Bing Fan
2021-07-23 16:47 ` Qian Cai
2021-07-26  7:17   ` Bing Fan
2021-07-26 16:39     ` Qian Cai [this message]
2021-07-26 20:36       ` Robin Murphy
2021-07-26 20:56         ` Qian Cai
2021-07-26 21:14           ` Robin Murphy
2021-07-27  2:57             ` Bing Fan
2021-08-12 14:31               ` Qian Cai
     [not found]                 ` <67cd6c830e33491e99ea4d2480f4a89d@tencent.com>
     [not found]                   ` <09918b566884413898f63b92ddd037a0@tencent.com>
2021-08-13 13:42                     ` [Internet]Re: " Qian Cai
2021-08-13 15:01                       ` gregkh
2021-08-13 15:09                         ` Robin Murphy
2021-08-13 15:14                           ` gregkh
2021-08-13 15:28                             ` Qian Cai

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=a1843494-5c8e-1ec8-5b98-df318db40922@quicinc.com \
    --to=quic_qiancai@quicinc.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hptsfb@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=tombinfan@tencent.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;
as well as URLs for NNTP newsgroup(s).