[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CH2PR12MB38958F0DC9CF4E82EDD793C8D76D9@CH2PR12MB3895.namprd12.prod.outlook.com>
Date: Thu, 18 Aug 2022 16:42:30 +0000
From: Asmaa Mnebhi <asmaa@...dia.com>
To: Wolfram Sang <wsa@...nel.org>
CC: Wolfram Sang <wsa+renesas@...g-engineering.com>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v1 0/7] i2c-mlxbf.c: bug fixes and new feature support
Sure!
-----Original Message-----
From: Wolfram Sang <wsa@...nel.org>
Sent: Thursday, August 18, 2022 12:24 PM
To: Asmaa Mnebhi <asmaa@...dia.com>
Cc: Wolfram Sang <wsa+renesas@...g-engineering.com>; linux-i2c@...r.kernel.org; linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 0/7] i2c-mlxbf.c: bug fixes and new feature support
Hi,
> Bug fixes:
> 1) Fix the frequency calculation
> 2) Fix incorrect base address passed during io write
> 3) prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
> 4) Support lock mechanism
If possible, the bugfixes should all come first so they can easily be backported. Also, they should have a Fixes: tag where possible.
If the above is possible, can you reorder, add Fixes tags and resend?
Happy hacking,
Wolfram
Powered by blists - more mailing lists