From: Michael Walle <michael@walle.cc>
To: "Vaibhaav Ram T.L" <vaibhaavram.tl@microchip.com>
Cc: gregkh@linuxfoundation.org, arnd@arndb.de,
kumaravel.thiagarajan@microchip.com,
tharunkumar.pasumarthi@microchip.com,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v11 char-misc-next 1/2] misc: microchip: pci1xxxx: Add support to read and write into PCI1XXXX OTP via NVMEM sysfs
Date: Mon, 08 May 2023 08:39:25 +0200 [thread overview]
Message-ID: <5445b9ad526aa1f4beaa47a3b0e7d83f@walle.cc> (raw)
In-Reply-To: <20230429120209.2232-2-vaibhaavram.tl@microchip.com>
Am 2023-04-29 14:02, schrieb Vaibhaav Ram T.L:
> From: Kumaravel Thiagarajan <kumaravel.thiagarajan@microchip.com>
>
> Microchip's pci1xxxx is an unmanaged PCIe3.1a switch for consumer,
> industrial, and automotive applications. This switch integrates OTP
> and EEPROM to enable customization of the part in the field. This
> patch adds support to read and write into PCI1XXXX OTP via NVMEM sysfs.
>
> Signed-off-by: Kumaravel Thiagarajan
> <kumaravel.thiagarajan@microchip.com>
> Co-developed-by: Tharun Kumar P <tharunkumar.pasumarthi@microchip.com>
> Signed-off-by: Tharun Kumar P <tharunkumar.pasumarthi@microchip.com>
> Co-developed-by: Vaibhaav Ram T.L <vaibhaavram.tl@microchip.com>
> Signed-off-by: Vaibhaav Ram T.L <vaibhaavram.tl@microchip.com>
I just had a quick look for obvious errors, couldn't spot any. It's
not a extensive review, though.
-michael
next parent reply other threads:[~2023-05-08 6:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230429120209.2232-1-vaibhaavram.tl@microchip.com>
[not found] ` <20230429120209.2232-2-vaibhaavram.tl@microchip.com>
2023-05-08 6:39 ` Michael Walle [this message]
[not found] ` <20230429120209.2232-3-vaibhaavram.tl@microchip.com>
2023-05-08 6:44 ` [PATCH v11 char-misc-next 2/2] misc: microchip: pci1xxxx: Add support to read and write into PCI1XXXX EEPROM via NVMEM sysfs Michael Walle
2023-05-15 14:44 ` VaibhaavRam.TL
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=5445b9ad526aa1f4beaa47a3b0e7d83f@walle.cc \
--to=michael@walle.cc \
--cc=UNGLinuxDriver@microchip.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kumaravel.thiagarajan@microchip.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tharunkumar.pasumarthi@microchip.com \
--cc=vaibhaavram.tl@microchip.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).