[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM6PR12MB3932054561C83FD4DA974B818CBA9@DM6PR12MB3932.namprd12.prod.outlook.com>
Date: Thu, 30 Jun 2022 08:06:41 +0000
From: "Guntupalli, Manikanta" <manikanta.guntupalli@....com>
To: Krzysztof Adamski <krzysztof.adamski@...ia.com>,
Manikanta Guntupalli <manikanta.guntupalli@...inx.com>,
"michal.simek@...inx.com" <michal.simek@...inx.com>,
"Simek, Michal" <michal.simek@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"git (AMD-Xilinx)" <git@....com>
CC: Raviteja Narayanam <raviteja.narayanam@...inx.com>
Subject: RE: [PATCH 02/12] i2c: xiic: Enter standard mode only for > 255 byte
read transfers
> -----Original Message-----
> From: Krzysztof Adamski <krzysztof.adamski@...ia.com>
> Sent: Wednesday, June 29, 2022 5:52 PM
> To: Manikanta Guntupalli <manikanta.guntupalli@...inx.com>;
> michal.simek@...inx.com; Simek, Michal <michal.simek@....com>; linux-
> arm-kernel@...ts.infradead.org; linux-i2c@...r.kernel.org; linux-
> kernel@...r.kernel.org; git (AMD-Xilinx) <git@....com>
> Cc: Raviteja Narayanam <raviteja.narayanam@...inx.com>
> Subject: Re: [PATCH 02/12] i2c: xiic: Enter standard mode only for > 255 byte
> read transfers
>
> CAUTION: This message has originated from an External Source. Please use
> proper judgment and caution when opening attachments, clicking links, or
> responding to this email.
>
>
> Hi,
>
> W dniu 24.06.2022 o 14:05, Manikanta Guntupalli pisze:
> > From: Raviteja Narayanam <raviteja.narayanam@...inx.com>
> >
> > To maintain backward compatibility the default transfer mode is
> > dynamic mode. Enter standard mode only when the size of read transfer
> > is > 255 bytes.
> >
> > Signed-off-by: Raviteja Narayanam <raviteja.narayanam@...inx.com>
> > Signed-off-by: Manikanta Guntupalli <manikanta.guntupalli@...inx.com>
>
> [...]
>
> I don't really understand why this patch isn't squashed into previous one. The
> previous patch was only checking the first message which was wrong, this
> one fixes that.
We will fix in V2
Thanks,
Manikanta.
Powered by blists - more mailing lists