From: Greg KH <gregkh@linuxfoundation.org>
To: Frank Wang <frank.wang@rock-chips.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
heikki.krogerus@linux.intel.com, sebastian.reichel@collabora.com,
heiko@sntech.de, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
huangtao@rock-chips.com, william.wu@rock-chips.com,
jianwei.zheng@rock-chips.com, yubing.zhang@rock-chips.com,
wmc@rock-chips.com
Subject: Re: usb: typec: tcpm: add get max power support
Date: Fri, 16 Jun 2023 08:05:07 +0200 [thread overview]
Message-ID: <2023061639-emerald-endorse-2f64@gregkh> (raw)
In-Reply-To: <45886fef-b84a-5704-0a08-100a20296323@rock-chips.com>
On Fri, Jun 16, 2023 at 11:13:08AM +0800, Frank Wang wrote:
> Hi Guenter,
>
> On 2023/6/16 10:26, Guenter Roeck wrote:
> > On 6/15/23 19:21, Frank Wang wrote:
> > > Traverse fixed pdos to calculate the maximum power that the charger
> > > can provide, and it can be got by POWER_SUPPLY_PROP_INPUT_POWER_LIMIT
> > > property.
> > >
> >
> > Wasn't this already v3 before ? What happened to the version, and the
> > change log ?
> > Or is this a completely different/new patch ?
> >
>
> Yes, it is the v3 patch before which has been hold for a long time, Gregkh
> asked me to rebase it and resubmit, so should I also add an "RESEND" tag in
> subject?
Yes, please do, otherwise we have no idea what is going on here.
Please resend v4 with all of the change information.
thanks,
greg k-h
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2023-06-16 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 2:21 usb: typec: tcpm: add get max power support Frank Wang
2023-06-16 2:26 ` Guenter Roeck
2023-06-16 3:13 ` Frank Wang
2023-06-16 6:05 ` Greg KH [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=2023061639-emerald-endorse-2f64@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=frank.wang@rock-chips.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jianwei.zheng@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sebastian.reichel@collabora.com \
--cc=william.wu@rock-chips.com \
--cc=wmc@rock-chips.com \
--cc=yubing.zhang@rock-chips.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