[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y+ON0TC30SOUzP91@kroah.com>
Date: Wed, 8 Feb 2023 12:56:01 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Tharunkumar.Pasumarthi@...rochip.com
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
On Tue, Feb 07, 2023 at 10:34:47AM +0000, Tharunkumar.Pasumarthi@...rochip.com wrote:
> > From: Tharunkumar Pasumarthi - I67821
> > Sent: Tuesday, February 7, 2023 3:22 PM
> > To: Greg KH <gregkh@...uxfoundation.org>
> > Subject: RE: [PATCH v3 char-misc-next] misc: microchip: pci1xxxx: Add
> > OTP/EEPROM driver for the pci1xxxx switch
> >
> > >
> > > 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?
>
> Sorry, I meant to ask if I could send V4 patch (not V3) addressing V3 comments.
You never need to ask if you can send a new patch series. It is
implied, always do so if changes have been made.
thanks,
greg k-h
Powered by blists - more mailing lists