linux-kernel - Re: [PATCH] i3c: transfer pid from boardinfo to device info

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <167335818715.550702.4568478412316741935.b4-ty@bootlin.com>
Date:   Tue, 10 Jan 2023 14:43:33 +0100
From:   Alexandre Belloni <alexandre.belloni@...tlin.com>
To:     Jack Chen <zenghuchen@...gle.com>
Cc:     linux-i3c@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Jesus Sanchez-Palencia <jesussanp@...gle.com>,
        Mark Slevinsky <markslevinsky@...gle.com>
Subject: Re: [PATCH] i3c: transfer pid from boardinfo to device info


On Thu, 05 Jan 2023 16:29:52 -0500, Jack Chen wrote:
> I3C device PID could be defined in device tree and stored in
> i3c_dev_boardinfo. It should be passed to i3c_device_info when
> allocating a i3c_dev_desc.
> Rational behind this change is: when users decide to use SETDASA to
> assign a dynamic address with exactly the original static address, in
> step of i3c_master_reattach_i3c_dev, this address is checked to be
> taken. Then device information retrieving step is skipped. As a result,
> though the i3c device is registered correctly, its device driver could
> not be probed.
> 
> [...]

Applied, thanks!

[1/1] i3c: transfer pid from boardinfo to device info
      commit: e826acc18bc7bdf4278bf8928caa3a0cd4065432

Best regards,

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com