[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <PH7PR11MB5958A72A7165DF1EF28724709BDB9@PH7PR11MB5958.namprd11.prod.outlook.com>
Date: Tue, 7 Feb 2023 09:52:18 +0000
From: <Tharunkumar.Pasumarthi@...rochip.com>
To: <gregkh@...uxfoundation.org>
CC: <Kumaravel.Thiagarajan@...rochip.com>, <arnd@...db.de>,
<linux-kernel@...r.kernel.org>, <linux-gpio@...r.kernel.org>,
<UNGLinuxDriver@...rochip.com>, <lkp@...el.com>
Subject: RE: [PATCH v3 char-misc-next] misc: microchip: pci1xxxx: Add
OTP/EEPROM driver for the pci1xxxx switch
> From: Greg KH <gregkh@...uxfoundation.org>
> Sent: Monday, February 6, 2023 11:19 PM
> To: Tharunkumar Pasumarthi - I67821
> <Tharunkumar.Pasumarthi@...rochip.com>
> Subject: Re: [PATCH v3 char-misc-next] misc: microchip: pci1xxxx: Add
> OTP/EEPROM driver for the pci1xxxx switch
>
> > This logic is not possible with normal timer functions. Timer wrapping
> > logic is handled by time_before API internally. So, there does not
> > seem to be issue with existing code.
>
> I have no context here as to what the code actually looked like anymore, so I
> do not know what is going on anymore, sorry.
Greg, I addressed all the comments received for V2 version of the patch (except for the one in discussion).
Shall I send V3 patch so that you will be able to get back previous context?
Thanks,
Tharun Kumar P
Powered by blists - more mailing lists