[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <76e96337-bbcf-89f1-2f1c-45144c15cb5b@ti.com>
Date: Thu, 5 Dec 2019 09:01:26 -0600
From: Dan Murphy <dmurphy@...com>
To: Marc Kleine-Budde <mkl@...gutronix.de>,
Sean Nyekjaer <sean@...nix.com>
CC: <linux-can@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<devicetree@...r.kernel.org>
Subject: Re: [PATCH 2/2] net: m_can: Make wake-up gpio an optional
Marc
On 12/5/19 8:39 AM, Marc Kleine-Budde wrote:
> On 12/5/19 2:26 PM, Dan Murphy wrote:
>> On 12/5/19 1:39 AM, Sean Nyekjaer wrote:
>>>
>>> On 04/12/2019 18.51, Dan Murphy wrote:
>>>> The device has the ability to disable the wake-up pin option.
>>>> The wake-up pin can be either force to GND or Vsup and does not have to
>>>> be tied to a GPIO. In order for the device to not use the wake-up
>>>> feature
>>>> write the register to disable the WAKE_CONFIG option.
>>>>
>>>> Signed-off-by: Dan Murphy <dmurphy@...com>
>>>> CC: Sean Nyekjaer <sean@...nix.com>
>>> Reviewed-by: Sean Nyekjaer <sean@...nix.com>
>>>> ---
>>>
>>> Hi Dan,
>>>
>>> I would add tcan4x5x to the subject of this patch ->
>>> "net: m_can: tcan4x5x Make wake-up gpio an optional"
>>>
>> Do you want me to submit v2 with the $subject change?
>>
>> Or would you fix it up when committing it?
> I'll change the subject while applying.
>
> Dan, what about maintainerchip of the tcan4x5?
Ooops that was buried in my inbox.
It only makes sense for someone from TI to take maintainership of the
TCAN device.
Do I need to submit a patch to the maintainers file or is the authorship
enough?
As far as a device what country do you reside in?
Dan
> regards,
> Marc
>
Powered by blists - more mailing lists