linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rjw@sisk.pl (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [git pull] Renesas DT changes for v3.5
Date: Thu, 19 Apr 2012 23:23:33 +0200	[thread overview]
Message-ID: <201204192323.33187.rjw@sisk.pl> (raw)
In-Reply-To: <CAOesGMitR0HT7HLCDX9sqohu9iJGPcQp8_TE3oS66ZhfvHizBQ@mail.gmail.com>

On Thursday, April 19, 2012, Olof Johansson wrote:
> Hi Rafael (and Magnus),
> 
> On Sun, Apr 15, 2012 at 2:20 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 
> > Magnus Damm (6):
> >      ARM: mach-shmobile: Introduce shmobile_setup_delay()
> >      ARM: mach-shmobile: Introduce INTC_IRQ_PINS_16H
> >      ARM: mach-shmobile: Use 0x3400 as INTCS vector offset
> >      ARM: mach-shmobile: Use INTC_IRQ_PINS_16H on sh7372
> >      ARM: mach-shmobile: Rework sh7372 INTCS demuxer V2
> >      ARM: mach-shmobile: sh7372 generic board support via DT V2
> 
> I noticed that none of these patches were posted beyond the shmobile
> mailing list.
> 
> We normally wouldn't care as much about patches that change various
> bit twiddling on the SoC specific parts, but for things like device
> tree conversion and bindings, it's useful to get more eyes on the
> changes.
> 
> Can you please cross-post on linux-arm-kernel at lists.infradead.org with
> these kind of platform changes so they get exposed to the wider set of
> readers? Also, once you start doing device bindings, they should be
> cross-posted to devicetree-discuss at lists.ozlabs.org.
> 
> The branch contents looks OK and I'll pull it in, but please start
> doing the above for new patches.

OK, we will.

Thanks,
Rafael

  reply	other threads:[~2012-04-19 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 21:20 [git pull] Renesas DT changes for v3.5 Rafael J. Wysocki
2012-04-19 21:07 ` Olof Johansson
2012-04-19 21:23   ` Rafael J. Wysocki [this message]
2012-04-22 20:14 ` Arnd Bergmann
2012-04-22 21:25   ` Rafael J. Wysocki

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=201204192323.33187.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-arm-kernel@lists.infradead.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).