devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Peddell <klightspeed-aslSrjg9ejhWX4hkXwHRhw@public.gmane.org>
To: Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>
Cc: Russell King <rmk+kernel-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM: Fix incorrect FDT initrd parameter override
Date: Tue, 14 Jan 2014 08:18:35 +1000	[thread overview]
Message-ID: <52D4663B.50108@killerwolves.net> (raw)
In-Reply-To: <20140113212834.GG19878-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>

On 14/01/2014 7:28 AM, Jason Cooper wrote:
> Ahhh, ok.  Thanks for the clarification.  You kept that line in the
> version you submitted to Russell's patch tracker?

Negative.  I'll supersede the patch with one including that line.

-- 
Ben Peddell
IT Support Bowen, Collinsville and Proserpine Catholic schools
http://klightspeed.killerwolves.net/
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2014-01-13 22:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11  0:03 [PATCH] ARM: Fix incorrect FDT initrd parameter override klightspeed-aslSrjg9ejhWX4hkXwHRhw
     [not found] ` <0a923e$51mtvt-73Sy8+Y76rVS+6ppBSHQ0E7lPHS7TK7L7bdBIQen8uI@public.gmane.org>
2014-01-13 15:28   ` Jason Cooper
     [not found]     ` <20140113152851.GF19878-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2014-01-13 21:08       ` Ben Peddell
     [not found]         ` <52D455CE.6090306-aslSrjg9ejhWX4hkXwHRhw@public.gmane.org>
2014-01-13 21:28           ` Jason Cooper
     [not found]             ` <20140113212834.GG19878-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2014-01-13 22:18               ` Ben Peddell [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=52D4663B.50108@killerwolves.net \
    --to=klightspeed-aslsrjg9ejhwx4hkxwhrhw@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=rmk+kernel-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.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).