From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] irqchip: armada-370-xp: Move the devicetree binding documentation
Date: Sun, 18 May 2014 20:37:58 -0300 [thread overview]
Message-ID: <20140518233757.GA630@arch.cereza> (raw)
In-Reply-To: <20140512144838.GA2689@arch.cereza>
On 12 May 11:48 AM, Ezequiel Garcia wrote:
> On 12 May 04:36 PM, Thomas Petazzoni wrote:
> > On Mon, 12 May 2014 11:27:40 -0300, Ezequiel Garcia wrote:
> > > Move the devicetree binding documentation to the interrupt-controller
> > > directory, where it belongs.
> > >
> > > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> > > ---
> > > .../devicetree/bindings/arm/armada-370-xp-mpic.txt | 38 ----------------------
> > > .../marvell,armada-370-xp-mpic.txt | 38 ++++++++++++++++++++++
> > > 2 files changed, 38 insertions(+), 38 deletions(-)
> > > delete mode 100644 Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt
> > > create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txt
> >
> > Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
> Thanks for reviewing!
>
> Ouch, before anyone complains, I've just realised I forgot to create the patch
> with the rename detection flag :-(
Jason,
Would you take this?
Thanks,
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-18 23:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 14:27 [PATCH] irqchip: armada-370-xp: Move the devicetree binding documentation Ezequiel Garcia
2014-05-12 14:36 ` Thomas Petazzoni
2014-05-12 14:48 ` Ezequiel Garcia
2014-05-18 23:37 ` Ezequiel Garcia [this message]
2014-05-18 23:40 ` Jason Cooper
2014-05-18 23:51 ` Ezequiel Garcia
2014-05-18 23:54 ` Jason Cooper
-- strict thread matches above, loose matches on Subject: below --
2014-05-19 0:02 Ezequiel Garcia
2014-05-19 2:10 ` Jason Cooper
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=20140518233757.GA630@arch.cereza \
--to=ezequiel.garcia@free-electrons.com \
--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