devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Kumar Gala <galak@codeaurora.org>
Cc: Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Olof Johansson <olof@lixom.net>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] of: Update qcom vendor prefix description
Date: Fri, 24 Jan 2014 13:34:24 -0600	[thread overview]
Message-ID: <CAL_JsqJMr8oAvFDs=LsBd8yPqXGBugueA08VLYTf0hdPrJn8_A@mail.gmail.com> (raw)
In-Reply-To: <7EA784E2-5108-4896-886A-444315793453@codeaurora.org>

On Fri, Jan 24, 2014 at 12:47 PM, Kumar Gala <galak@codeaurora.org> wrote:
>
> On Dec 18, 2013, at 5:50 PM, Olof Johansson <olof@lixom.net> wrote:
>
>> On Wed, Dec 18, 2013 at 3:41 PM, Kumar Gala <galak@codeaurora.org> wrote:
>>> Update vendor description to be the full name of the corporate entity that
>>> produces the SoCs associated with this prefix.
>>>
>>> Signed-off-by: Kumar Gala <galak@codeaurora.org>
>>
>> Acked-by: Olof Johansson <olof@lixom.net>
>>
>>
>> -Olof
>> --
>> To unsubscribe from this list: send the line "unsubscribe devicetree" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> Rob,
>
> Did this get lost, haven’t seen it applied
>

Ah, sorry. I'll send it for 3.14-rc.

Rob

      reply	other threads:[~2014-01-24 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 23:41 [PATCH] of: Update qcom vendor prefix description Kumar Gala
2013-12-18 23:50 ` Olof Johansson
2014-01-24 18:47   ` Kumar Gala
2014-01-24 19:34     ` Rob Herring [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='CAL_JsqJMr8oAvFDs=LsBd8yPqXGBugueA08VLYTf0hdPrJn8_A@mail.gmail.com' \
    --to=robherring2@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=pawel.moll@arm.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).