From: Greg KH <gregkh@linuxfoundation.org>
To: Tharunkumar.Pasumarthi@microchip.com
Cc: Kumaravel.Thiagarajan@microchip.com, arnd@arndb.de,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
UNGLinuxDriver@microchip.com, lkp@intel.com
Subject: Re: [PATCH v3 char-misc-next] misc: microchip: pci1xxxx: Add OTP/EEPROM driver for the pci1xxxx switch
Date: Wed, 8 Feb 2023 12:56:01 +0100 [thread overview]
Message-ID: <Y+ON0TC30SOUzP91@kroah.com> (raw)
In-Reply-To: <PH7PR11MB5958A5B33798411DE2EBC90E9BDB9@PH7PR11MB5958.namprd11.prod.outlook.com>
On Tue, Feb 07, 2023 at 10:34:47AM +0000, Tharunkumar.Pasumarthi@microchip.com wrote:
> > From: Tharunkumar Pasumarthi - I67821
> > Sent: Tuesday, February 7, 2023 3:22 PM
> > To: Greg KH <gregkh@linuxfoundation.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
next prev parent reply other threads:[~2023-02-08 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 19:29 [PATCH v3 char-misc-next] misc: microchip: pci1xxxx: Add OTP/EEPROM driver for the pci1xxxx switch Kumaravel Thiagarajan
2023-01-20 10:55 ` Greg KH
2023-02-06 9:20 ` Tharunkumar.Pasumarthi
2023-02-06 9:41 ` Greg KH
2023-02-06 17:03 ` Tharunkumar.Pasumarthi
2023-02-06 17:48 ` Greg KH
2023-02-07 9:52 ` Tharunkumar.Pasumarthi
2023-02-07 10:34 ` Tharunkumar.Pasumarthi
2023-02-08 11:56 ` Greg KH [this message]
2023-02-07 13:45 ` Michael Walle
2023-02-08 6:43 ` Tharunkumar.Pasumarthi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+ON0TC30SOUzP91@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Kumaravel.Thiagarajan@microchip.com \
--cc=Tharunkumar.Pasumarthi@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=arnd@arndb.de \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).