From: Dan Murphy <dmurphy@ti.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>, Sean Nyekjaer <sean@geanix.com>
Cc: linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] net: m_can: Make wake-up gpio an optional
Date: Thu, 5 Dec 2019 09:01:26 -0600 [thread overview]
Message-ID: <76e96337-bbcf-89f1-2f1c-45144c15cb5b@ti.com> (raw)
In-Reply-To: <809b9ff1-88e3-4e46-33e0-856db37898b2@pengutronix.de>
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@ti.com>
>>>> CC: Sean Nyekjaer <sean@geanix.com>
>>> Reviewed-by: Sean Nyekjaer <sean@geanix.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
>
WARNING: multiple messages have this Message-ID (diff)
From: Dan Murphy <dmurphy@ti.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>, Sean Nyekjaer <sean@geanix.com>
Cc: <linux-can@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] net: m_can: Make wake-up gpio an optional
Date: Thu, 5 Dec 2019 09:01:26 -0600 [thread overview]
Message-ID: <76e96337-bbcf-89f1-2f1c-45144c15cb5b@ti.com> (raw)
In-Reply-To: <809b9ff1-88e3-4e46-33e0-856db37898b2@pengutronix.de>
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@ti.com>
>>>> CC: Sean Nyekjaer <sean@geanix.com>
>>> Reviewed-by: Sean Nyekjaer <sean@geanix.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
>
next prev parent reply other threads:[~2019-12-05 15:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 17:51 [PATCH 1/2] dt-bindings: tcan4x5x: Make wake-gpio an optional gpio Dan Murphy
2019-12-04 17:51 ` Dan Murphy
2019-12-04 17:51 ` [PATCH 2/2] net: m_can: Make wake-up gpio an optional Dan Murphy
2019-12-04 17:51 ` Dan Murphy
2019-12-05 7:39 ` Sean Nyekjaer
2019-12-05 13:26 ` Dan Murphy
2019-12-05 13:26 ` Dan Murphy
2019-12-05 14:39 ` Marc Kleine-Budde
2019-12-05 15:01 ` Dan Murphy [this message]
2019-12-05 15:01 ` Dan Murphy
2019-12-05 15:35 ` Marc Kleine-Budde
2019-12-09 21:01 ` Dan Murphy
2019-12-09 21:01 ` Dan Murphy
2019-12-09 21:06 ` Marc Kleine-Budde
2019-12-09 21:07 ` Dan Murphy
2019-12-09 21:07 ` Dan Murphy
2019-12-09 21:10 ` Marc Kleine-Budde
2019-12-05 7:36 ` [PATCH 1/2] dt-bindings: tcan4x5x: Make wake-gpio an optional gpio Sean Nyekjaer
2019-12-06 13:49 ` Sean Nyekjaer
2019-12-06 13:49 ` Sean Nyekjaer
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=76e96337-bbcf-89f1-2f1c-45144c15cb5b@ti.com \
--to=dmurphy@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=sean@geanix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.