From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Linus Walleij <linus.walleij@linaro.org>,
"Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Saravana Kannan <saravanak@google.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <patches@armlinux.org.uk>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH v2] ARM: Add sanity check for dev->periphid in amba_probe()
Date: Tue, 30 Aug 2022 19:49:02 +0800 [thread overview]
Message-ID: <81775dd3-d9ef-36d7-bdc7-b578c5d617a5@huawei.com> (raw)
In-Reply-To: <CACRpkdYhx4zT9F1CTEvAPjB1EmBD6CFenTJpwQ-KPg1+zCsYGg@mail.gmail.com>
On 2022/8/30 19:19, Linus Walleij wrote:
> On Tue, Aug 30, 2022 at 12:37 PM Russell King (Oracle)
> <linux@armlinux.org.uk> wrote:
>
>>> ... ...
>>> driver_probe_device(drv, dev);
>>> ......
>>> dev->bus->probe
>>
>> And that makes no sense, is an already known issue, and there is a patch
>> to fix it:
>>
>> https://lore.kernel.org/all/20220817184026.3468620-1-isaacmanjarres@google.com/
>
> This patch to the driver core fixes my QEMU issue as well, I'll try
> to reply in-thread. Thanks for pointing this out Russell!
OK, so that my patch can be dropped.
>
> Yours,
> Linus Walleij
> .
>
--
Regards,
Zhen Lei
next prev parent reply other threads:[~2022-08-30 11:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 6:54 Zhen Lei
2022-08-30 7:20 ` Saravana Kannan
2022-08-30 9:47 ` Russell King (Oracle)
2022-08-30 9:48 ` Russell King (Oracle)
2022-08-30 10:03 ` Leizhen (ThunderTown)
2022-08-30 10:07 ` Russell King (Oracle)
2022-08-30 10:31 ` Leizhen (ThunderTown)
2022-08-30 10:36 ` Russell King (Oracle)
2022-08-30 11:19 ` Linus Walleij
2022-08-30 11:49 ` Leizhen (ThunderTown) [this message]
2022-08-30 17:34 ` Saravana Kannan
2022-08-30 23:48 ` Saravana Kannan
2022-08-30 9:50 ` Russell King (Oracle)
2022-08-30 10:07 ` Leizhen (ThunderTown)
2022-08-30 12:11 ` Leizhen (ThunderTown)
2022-08-30 10:28 ` Russell King (Oracle)
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=81775dd3-d9ef-36d7-bdc7-b578c5d617a5@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=patches@armlinux.org.uk \
--cc=saravanak@google.com \
--cc=wangkefeng.wang@huawei.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
all inboxes | Powered by JetHome®