From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Prashant Malani <pmalani@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
gregkh@linuxfoundation.org, bleung@chromium.org
Subject: Re: [PATCH v4 1/2] usb: typec: Consolidate sysfs ABI documentation
Date: Wed, 25 Nov 2020 09:53:12 +0200 [thread overview]
Message-ID: <20201125075312.GF1008337@kuha.fi.intel.com> (raw)
In-Reply-To: <20201125074603.GE1008337@kuha.fi.intel.com>
On Wed, Nov 25, 2020 at 09:46:06AM +0200, Heikki Krogerus wrote:
> On Tue, Nov 24, 2020 at 12:32:35PM -0800, Prashant Malani wrote:
> > Hi,
> >
> > On Tue, Nov 24, 2020 at 12:10:31PM -0800, Prashant Malani wrote:
> > > Both partner and cable have identity VDOs. These are listed separately
> > > in the Documentation/ABI/testing/sysfs-class-typec. Factor these out
> > > into a common location to avoid the duplication.
> > >
> > > Signed-off-by: Prashant Malani <pmalani@chromium.org>
> > > Acked-by: Heikki Krogerus <heikki.krogeurus@linux.intel.com>
> > I copied the Acked-by line from v3 [1] as is, but looks like there was a
> > typo there and the email address should be
> > "heikki.krogerus@linux.intel.com".
> >
> > Please let me know if it's fine as is or whether I should send another
> > patchset.
>
> It is fine. Thanks for taking care of that :-)
Arch, no. It's not fine (I don't know what I'm talking about there). I
think it would be better that you do resend.
thanks,
--
heikki
next prev parent reply other threads:[~2020-11-25 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 20:10 [PATCH v4 1/2] usb: typec: Consolidate sysfs ABI documentation Prashant Malani
2020-11-24 20:10 ` [PATCH v4 2/2] usb: typec: Expose Product Type VDOs via sysfs Prashant Malani
2020-11-24 20:32 ` [PATCH v4 1/2] usb: typec: Consolidate sysfs ABI documentation Prashant Malani
2020-11-25 7:46 ` Heikki Krogerus
2020-11-25 7:53 ` Heikki Krogerus [this message]
2020-11-25 8:50 ` Prashant Malani
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=20201125075312.GF1008337@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=bleung@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmalani@chromium.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).