linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Ajay Gupta <ajaykuee@gmail.com>
Cc: heikki.krogerus@linux.intel.com, linux-usb@vger.kernel.org,
	linux-i2c@vger.kernel.org, Ajay Gupta <ajayg@nvidia.com>
Subject: Re: [PATCH v5 0/5] usb: typec: ucsi: ccg: add runtime pm support
Date: Sat, 8 Jun 2019 00:10:43 +0200	[thread overview]
Message-ID: <20190607221043.GA869@kunai> (raw)
In-Reply-To: <20190607163423.31860-1-ajayg@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

On Fri, Jun 07, 2019 at 09:34:18AM -0700, Ajay Gupta wrote:
> Hi Heikki and Wolfram
> The latest set (v5) fix comments from Wolfram on further refactoring
> master_xfer() function in i2c-nvidia-gpuc.c file and removing extra comments
> in patch 2/5.
> 
> Patches can go through either usb or i2c tree but since there are 3 out of 5
> patches from i2c so may be better they go through i2c. They all should go
> together.
> 
> Thanks
> Ajay

Applied the series to i2c/for-next, thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2019-06-07 22:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 16:34 [PATCH v5 0/5] usb: typec: ucsi: ccg: add runtime pm support Ajay Gupta
2019-06-07 16:34 ` [PATCH v5 1/5] i2c: nvidia-gpu: refactor master_xfer Ajay Gupta
2019-06-07 16:34 ` [PATCH v5 2/5] i2c: nvidia-gpu: add runtime pm support Ajay Gupta
2019-06-07 16:34 ` [PATCH v5 3/5] usb: typec: ucsi: ccg: enable " Ajay Gupta
2019-06-07 16:34 ` [PATCH v5 4/5] i2c: nvidia-gpu: resume ccgx i2c client Ajay Gupta
2019-06-07 16:34 ` [PATCH v5 5/5] usb: typec: ucsi: ccg: add runtime pm workaround Ajay Gupta
2019-06-07 22:10 ` Wolfram Sang [this message]

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=20190607221043.GA869@kunai \
    --to=wsa@the-dreams.de \
    --cc=ajayg@nvidia.com \
    --cc=ajaykuee@gmail.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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).