linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Aswath Govindraju <a-govindraju@ti.com>,
	Lokesh Vutla <lokeshvutla@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Chandrasekar Ramakrishnan <rcsekar@samsung.com>,
	Wolfgang Grandegger <wg@grandegger.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Sriram Dash <sriram.dash@samsung.com>,
	<linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: net: can: Document power-domains property
Date: Wed, 4 Aug 2021 10:49:27 -0500	[thread overview]
Message-ID: <20210804154927.w5jtppcc6n6qh7mf@never> (raw)
In-Reply-To: <20210804072341.l4flosh7rkvma22o@pengutronix.de>

On 09:23-20210804, Marc Kleine-Budde wrote:
> On 02.08.2021 14:48:22, Aswath Govindraju wrote:
> > Document power-domains property for adding the Power domain provider.
> > 
> > Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
> 
> Applied to linux-can-next/testing.
> 
> BTW: TI's dkim is broken:
> 
> |   ✗ [PATCH v2] dt-bindings: net: can: Document power-domains property
> |     + Link: https://lore.kernel.org/r/20210802091822.16407-1-a-govindraju@ti.com
> |     + Acked-by: Rob Herring <robh@kernel.org>
> |     + Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> |   ---
> |   ✗ BADSIG: DKIM/ti.com
> 

I have taken this up with TI's IT operations folks, Thanks for the headsup.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

      reply	other threads:[~2021-08-04 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02  9:18 [PATCH v2] dt-bindings: net: can: Document power-domains property Aswath Govindraju
2021-08-03 20:37 ` Rob Herring
2021-08-04  7:23 ` Marc Kleine-Budde
2021-08-04 15:49   ` Nishanth Menon [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=20210804154927.w5jtppcc6n6qh7mf@never \
    --to=nm@ti.com \
    --cc=a-govindraju@ti.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=rcsekar@samsung.com \
    --cc=robh+dt@kernel.org \
    --cc=sriram.dash@samsung.com \
    --cc=vigneshr@ti.com \
    --cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).