linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: cy_huang <u0084500@gmail.com>
Cc: gregkh@linuxfoundation.org, robh+dt@kernel.org,
	matthias.bgg@gmail.com, linux@roeck-us.net, cy_huang@richtek.com,
	gene_chen@richtek.com, linux-usb@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] usb typec: mt6360: Add support for mt6360 Type-C driver
Date: Thu, 27 Aug 2020 17:00:01 +0300	[thread overview]
Message-ID: <20200827140001.GE813478@kuha.fi.intel.com> (raw)
In-Reply-To: <1598527137-6915-1-git-send-email-u0084500@gmail.com>

On Thu, Aug 27, 2020 at 07:18:55PM +0800, cy_huang wrote:
> From: ChiYuan Huang <cy_huang@richtek.com>
> 
> Mediatek MT6360 is a multi-functional IC that includes USB Type-C.
> It works with Type-C Port Controller Manager to provide USB PD
> and USB Type-C functionalities.
> 
> v1 to v2
> 1. Add fix to Prevent the race condition from interrupt and tcpci port
> unregister during module remove.
> 
> v2 to v3
> 1. Change comment style for the head of source code.
> 2. No need to print error for platform_get_irq_byname.
> 3. Fix tcpci_register_port check from IS_ERR_OR_NULL to IS_ERR.
> 4. Rename driver/Kconfig/Makefile form mt6360 to mt636x.
> 5. Rename DT binding documents from mt6360 to mt636x.

You don't place additional changelog here...

> Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
> ---

You put it here, after that '---' marker:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#the-canonical-patch-format


>  drivers/usb/typec/tcpm/Kconfig        |   8 ++
>  drivers/usb/typec/tcpm/Makefile       |   1 +
>  drivers/usb/typec/tcpm/tcpci_mt6360.c | 212 ++++++++++++++++++++++++++++++++++
>  3 files changed, 221 insertions(+)
>  create mode 100644 drivers/usb/typec/tcpm/tcpci_mt6360.c

thanks,

-- 
heikki

  parent reply	other threads:[~2020-08-27 14:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 11:18 [PATCH v3 1/3] usb typec: mt6360: Add support for mt6360 Type-C driver cy_huang
2020-08-27 11:18 ` [PATCH v3 2/3] usb typec: mt6360: Rename driver/Kconfig/Makefile from mt6360 to mt636x cy_huang
2020-08-27 16:41   ` Guenter Roeck
2020-08-28  5:54     ` ChiYuan Huang
2020-08-27 11:18 ` [PATCH v3 3/3] usb typec: mt6360: Add MT6360 Type-C DT binding documentation cy_huang
2020-08-27 14:00 ` Heikki Krogerus [this message]
2020-08-27 14:51   ` [PATCH v3 1/3] usb typec: mt6360: Add support for mt6360 Type-C driver ChiYuan Huang
2020-08-28  9:38     ` Heikki Krogerus
2020-08-28 10:27       ` ChiYuan Huang
2020-08-28 11:57         ` Heikki Krogerus
2020-08-28 12:10 ` Chunfeng Yun
2020-08-28 14:33   ` ChiYuan Huang
2020-08-28 14:48     ` Guenter Roeck

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=20200827140001.GE813478@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=cy_huang@richtek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gene_chen@richtek.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=u0084500@gmail.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).