devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: grant.likely@secretlab.ca
Cc: linux-kernel@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org, sparclinux@vger.kernel.org,
	benh@kernel.crashing.org
Subject: Re: [PATCH] drivers/of: Constify device_node->name and ->path_component_name
Date: Wed, 14 Nov 2012 17:33:04 -0500 (EST)	[thread overview]
Message-ID: <20121114.173304.405703188822325414.davem@davemloft.net> (raw)
In-Reply-To: <1352932107-14782-1-git-send-email-grant.likely@secretlab.ca>


You're making other changes here, such as the kstrdup() stuff,
seperate that into another patch.

  reply	other threads:[~2012-11-14 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 22:28 [PATCH] drivers/of: Constify device_node->name and ->path_component_name Grant Likely
2012-11-14 22:33 ` David Miller [this message]
2012-11-14 22:42   ` Grant Likely
2012-11-14 22:46     ` Julian Calaby
2012-11-14 22:48       ` Grant Likely
2012-11-14 22:49     ` David Miller

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=20121114.173304.405703188822325414.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=benh@kernel.crashing.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    /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).