All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Xiubo Li <Li.Xiubo@freescale.com>,
	mark.rutland@arm.com, gregkh@linuxfoundation.org,
	mpa@pengutronix.de, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 0/2] add DT endianness binding support
Date: Thu, 1 May 2014 05:43:58 +0200	[thread overview]
Message-ID: <20140501034358.GA4514@netboy> (raw)
In-Reply-To: <20140430182500.GD3245@sirena.org.uk>

On Wed, Apr 30, 2014 at 11:25:00AM -0700, Mark Brown wrote:
> On Wed, Apr 30, 2014 at 09:10:12AM +0200, Richard Cochran wrote:
> > Shouldn't this go to the arm list and rmk for review, too?
> 
> Is there any particular reason for including rmk?  It's generally not
> helpful to spam people with serieses without reason, we all get quite a
> lot of mail already...

I recall seeing him writing at length about cpu/peripheral endianness
issues, so I assume he has some expertise here. It would be a shame if
a new DT feature were overlooking something important.

Thanks,
Richard

      reply	other threads:[~2014-05-01  3:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30  4:43 [PATCHv3 0/2] add DT endianness binding support Xiubo Li
2014-04-30  4:43 ` Xiubo Li
2014-04-30  4:43 ` [PATCHv3 1/2] dt/bindings: Add the DT binding documentation for endianness Xiubo Li
2014-04-30  4:43   ` Xiubo Li
2014-04-30  4:43 ` [PATCHv3 2/2] regmap: add DT endianness binding support Xiubo Li
2014-04-30  4:43   ` Xiubo Li
2014-04-30  6:56   ` Markus Pargmann
2014-04-30  7:10     ` Li.Xiubo
2014-04-30  7:10       ` Li.Xiubo
2014-04-30  7:10 ` [PATCHv3 0/2] " Richard Cochran
2014-04-30  7:14   ` Li.Xiubo
2014-04-30  9:26     ` Richard Cochran
2014-04-30 13:46     ` Richard Cochran
2014-04-30 18:25   ` Mark Brown
2014-05-01  3:43     ` Richard Cochran [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=20140501034358.GA4514@netboy \
    --to=richardcochran@gmail.com \
    --cc=Li.Xiubo@freescale.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mpa@pengutronix.de \
    /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.