[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <273be5a6-c45f-8f12-361f-65caf0c3d08b@intel.com>
Date: Mon, 5 Jul 2021 15:13:25 +0800
From: Jie Deng <jie.deng@...el.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: linux-i2c@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, wsa@...nel.org,
wsa+renesas@...g-engineering.com, mst@...hat.com, arnd@...db.de,
jasowang@...hat.com, andriy.shevchenko@...ux.intel.com,
yu1.wang@...el.com, shuo.a.liu@...el.com, conghui.chen@...el.com,
stefanha@...hat.com
Subject: Re: [PATCH v12] i2c: virtio: add a virtio i2c frontend driver
On 2021/7/5 14:30, Viresh Kumar wrote:
>>
>> This is still not enough to convince me. So I won't change them for now
>> until I see it
>>
>> is the consensus of the majority.
> Do you see reqs[i] to ever be NULL here ? If not, then if (req) is like if
> (true).
>
> Why would you want to have something like that ?
No. Currently, virtio_i2c_complete_reqs is only called by
virtio_i2c_xfer, thus we don't
have reqs[i] to be NULL. But I think "virtio_i2c_complete_reqs" as an
independent function
should consider this from a callee perspective.
Anyway, if you really think it should be changed, it can be fixed
incrementally as Wolfram said.
Powered by blists - more mailing lists