From: Jinpu Wang <jinpu.wang@cloud.ionos.com>
To: Deepak Ukey <deepak.ukey@microchip.com>
Cc: Linux SCSI Mailinglist <linux-scsi@vger.kernel.org>,
Vasanthalakshmi.Tharmarajan@microchip.com,
Viswas G <Viswas.G@microchip.com>,
Jack Wang <jinpu.wang@profitbricks.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
dpf@google.com, yuuzheng@google.com,
Vikram Auradkar <auradkar@google.com>,
vishakhavc@google.com, bjashnani@google.com,
Radha Ramachandran <radha@google.com>,
akshatzen@google.com
Subject: Re: [PATCH 12/12] pm80xx : IOCTL functionality for TWI device.
Date: Thu, 2 Jan 2020 13:20:53 +0100 [thread overview]
Message-ID: <CAMGffE=7egBpma-=KHySYW0QTsqqHhy4yZnZMSnw19ayxYgYMQ@mail.gmail.com> (raw)
In-Reply-To: <20191224044143.8178-13-deepak.ukey@microchip.com>
On Tue, Dec 24, 2019 at 5:41 AM Deepak Ukey <deepak.ukey@microchip.com> wrote:
>
> From: Viswas G <Viswas.G@microchip.com>
>
> Added the IOCTL functionality for TWI device.
>
Please extend the commit message, what's the new functionality, what's
the use case.
Thanks
next prev parent reply other threads:[~2020-01-02 12:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 4:41 [PATCH 00/12] pm80xx : Updates for the driver version 0.1.39 Deepak Ukey
2019-12-24 4:41 ` [PATCH 01/12] pm80xx : Increase request sg length Deepak Ukey
2019-12-25 15:57 ` kbuild test robot
2019-12-24 4:41 ` [PATCH 02/12] pm80xx : Deal with kexec reboots Deepak Ukey
2020-01-02 11:52 ` Jinpu Wang
2019-12-24 4:41 ` [PATCH 03/12] pm80xx : Free the tag when mpi_set_phy_profile_resp is received Deepak Ukey
2020-01-02 11:55 ` Jinpu Wang
2019-12-24 4:41 ` [PATCH 04/12] pm80xx : Cleanup initialization loading fail path Deepak Ukey
2020-01-02 11:58 ` Jinpu Wang
2019-12-24 4:41 ` [PATCH 05/12] pm80xx : Support for char device Deepak Ukey
2020-01-02 12:03 ` Jinpu Wang
2019-12-24 4:41 ` [PATCH 06/12] pm80xx : sysfs attribute for number of phys Deepak Ukey
2020-01-02 12:07 ` Jinpu Wang
2020-01-02 12:33 ` John Garry
2020-01-02 16:38 ` Viswas.G
2020-01-13 9:26 ` Deepak.Ukey
2020-01-13 9:39 ` Jinpu Wang
2019-12-24 4:41 ` [PATCH 07/12] pm80xx : IOCTL functionality to get phy profile Deepak Ukey
2020-01-02 12:10 ` Jinpu Wang
2020-01-02 16:42 ` Viswas.G
2019-12-24 4:41 ` [PATCH 08/12] pm80xx : IOCTL functionality for GPIO Deepak Ukey
2020-01-06 16:25 ` Jinpu Wang
2020-01-06 16:39 ` Jinpu Wang
2019-12-24 4:41 ` [PATCH 09/12] pm80xx : IOCTL functionality for SGPIO Deepak Ukey
2019-12-30 2:47 ` Nathan Chancellor
2020-01-06 16:30 ` Jinpu Wang
2019-12-24 4:41 ` [PATCH 10/12] pm80xx : sysfs attribute for non fatal dump Deepak Ukey
2020-01-06 16:34 ` Jinpu Wang
2019-12-24 4:41 ` [PATCH 11/12] pm80xx : Introduce read and write length for IOCTL payload structure Deepak Ukey
2020-01-06 16:35 ` Jinpu Wang
2019-12-24 4:41 ` [PATCH 12/12] pm80xx : IOCTL functionality for TWI device Deepak Ukey
2020-01-02 12:20 ` Jinpu Wang [this message]
2020-01-02 16:41 ` Viswas.G
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='CAMGffE=7egBpma-=KHySYW0QTsqqHhy4yZnZMSnw19ayxYgYMQ@mail.gmail.com' \
--to=jinpu.wang@cloud.ionos.com \
--cc=Vasanthalakshmi.Tharmarajan@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=akshatzen@google.com \
--cc=auradkar@google.com \
--cc=bjashnani@google.com \
--cc=deepak.ukey@microchip.com \
--cc=dpf@google.com \
--cc=jinpu.wang@profitbricks.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=radha@google.com \
--cc=vishakhavc@google.com \
--cc=yuuzheng@google.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).