linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sricharan R <r.sricharan@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Olof Johansson <olof@lixom.net>,
	linux-omap@vger.kernel.org, arm@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 4/4] omap crossbar support for v3.15
Date: Tue, 11 Mar 2014 18:11:56 +0530	[thread overview]
Message-ID: <531F0494.1040105@ti.com> (raw)
In-Reply-To: <20140310163620.GB4882@atomide.com>

Tony,

On Monday 10 March 2014 10:06 PM, Tony Lindgren wrote:
> * Olof Johansson <olof@lixom.net> [140308 23:36]:
>> On Sun, Mar 02, 2014 at 03:14:49PM -0800, Tony Lindgren wrote:
>>> The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:
>>>
>>>   Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)
>>>
>>> are available in the git repository at:
>>>
>>>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.15/crossbar-signed
>>>
>>> for you to fetch changes up to 9594274201ac3c67d5c569aae63792e58bcd33e6:
>>>
>>>   Merge branch 'crossbar_3.14_rc1' of git://github.com/Sricharanti/sricharan into omap-for-v3.15/crossbar (2014-02-28 13:35:02 -0800)
>>>
>>> ----------------------------------------------------------------
>>>
>>> Add support for GIC crossbar that routes interrupts on newer omaps.
>>>
>>> Looks like people wanted these merged via the omap tree as it's
>>> the only user for the GIC crossbar.
>>>
>>> ----------------------------------------------------------------
>>> Sricharan R (4):
>>>       DRIVERS: IRQCHIP: IRQ-GIC: Add support for routable irqs
>>>       DRIVERS: IRQCHIP: CROSSBAR: Add support for Crossbar IP
>>>       ARM: OMAP4+: Correct Wakeup-gen code to use physical irq number
>>>       ARM: DRA: Enable Crossbar IP support for DRA7XX
>> Whoa, lots of caps on those driver subjects. I don't think we need those
>> in the future, lower case is just fine (and DRIVERS: usually isn't used).
> Oops yeah I had them as "irqchip: crossbar" and "irqchip: irq-gic" in
> my earlier branch for v3.14 that did not get merged, but this time I
> pulled from Sricharan.
>
> Scricharan, maybe use less yelling naming for any follow-up patches?
>  
  Will make sure that there are no caps in the follow up patches.

Regards,
 Sricharan

  reply	other threads:[~2014-03-11 12:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pull-1393802089-910509>
2014-03-03  0:10 ` [GIT PULL 3/4] omap device tree changes for v3.15 Tony Lindgren
2014-03-09  7:29   ` Olof Johansson
     [not found] ` <5313bcc3.c5bf440a.7302.4a69SMTPIN_ADDED_MISSING@mx.google.com>
2014-03-09  7:18   ` [GIT PULL 2/4] omap prcm " Olof Johansson
     [not found] ` <5313bcc4.66ff420a.7636.3ca9SMTPIN_ADDED_MISSING@mx.google.com>
2014-03-09  7:26   ` [GIT PULL 3/4] omap device tree " Olof Johansson
     [not found] ` <5313bcc5.a8fc440a.467f.7ba2SMTPIN_ADDED_MISSING@mx.google.com>
2014-03-09  7:33   ` [GIT PULL 4/4] omap crossbar support " Olof Johansson
2014-03-10 16:36     ` Tony Lindgren
2014-03-11 12:41       ` Sricharan R [this message]
2014-05-05 14:28         ` Sricharan R
2014-05-05 14:30           ` Sricharan R

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=531F0494.1040105@ti.com \
    --to=r.sricharan@ti.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=tony@atomide.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).