[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPTae5Lmwi5qa=RUym+hr_gh2R=OX1VuBQ9XXAJ9xVAH+Hjp5g@mail.gmail.com>
Date: Sat, 27 May 2017 13:34:43 -0700
From: Badhri Jagan Sridharan <badhri@...gle.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Guenter Roeck <linux@...ck-us.net>,
Oliver Neukum <oneukum@...e.com>,
USB <linux-usb@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCHv4] usb: typec: Add a sysfs node to manage port type
On Fri, May 26, 2017 at 10:43 PM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Fri, May 26, 2017 at 01:42:57PM -0700, Badhri Jagan Sridharan wrote:
>> User space applications in some cases have the need to enforce a
>> specific port type(DFP/UFP/DRP). This change allows userspace to
>> attempt setting the desired port type. Low level drivers can
>> however reject the request if the specific port type is not supported.
>>
>> Signed-off-by: Badhri Jagan Sridharan <Badhri@...gle.com>
>> ---
>> Changelog since v1:
>> - introduced a new variable port_type in struct typec_port to track
>> the current port type instead of changing type member in
>> typec_capability to address Heikki Krogerus comments.
>> - changed the output format and strings that would be displayed as
>> suggested by Heikki Krogerus.
>>
>> Changelog since v2:
>> - introduced a new mutex lock to protect port_type for addressing
>> the race conditions identified by Geunter Roeck
>> - added typec_port_types_drp for printing port_type when cap->type
>> is TYPE_PORT_DRP as suggested by Geunter Roeck
>> - Power role swap and data role swaps would be rejected unless
>> port port_type == TYPE_PORT_DRP
>> - port_type_store would return immediately if the current port_type
>> is same as the new port_type as suggested by Geunter Roeck
>>
>> Changelog since v3:
>> - Moved as much as code outside port_type_lock as suggested by
>> Geunter Roeck
>> - Removed Change-Id line from commit message identified by
>> Greg Kroah-Hartman
>
> Ok, this is how you write a changelog for a patch, very nice job!
Thanks Greg :)
>
> greg k-h
Powered by blists - more mailing lists