linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sean@mess.org (Sean Young)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] Documentation: devicetree: meson-ir: "linux,rc-map-name" is supported
Date: Wed, 1 Feb 2017 22:49:57 +0000	[thread overview]
Message-ID: <20170201224957.GA3631@gofer.mess.org> (raw)
In-Reply-To: <CAFBinCDF2d36E2hp7w_ehqdErdZPK9maQLpBmqMoGMPZmTTqqQ@mail.gmail.com>

On Wed, Feb 01, 2017 at 11:26:14PM +0100, Martin Blumenstingl wrote:
> On Wed, Feb 1, 2017 at 11:14 PM, Martin Blumenstingl
> <martin.blumenstingl@googlemail.com> wrote:
> > The driver already parses the "linux,rc-map-name" property. Add this
> > information to the documentation so .dts maintainers don't have to look
> > it up in the source-code.
> >
> > Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> > Acked-by: Rob Herring <robh@kernel.org>
> > ---
> > Changes since v1:
> > - removed character which shows up as whitespace from subject
> I have verified that I really sent this without a whitespace (I'm
> using git send-email, so the patch is not mangled by some webmailer) -
> unfortunately it seems to appear again (maybe one of the receiving
> mail-servers or the mailing-list software does something weird here).
> 
> @Mauro: can you handle this when you merge the patch - or do you want
> me to push this to some git repo from which you can pull?

I'll apply it to my rc-tree and fix up any problems.


Sean

  reply	other threads:[~2017-02-01 22:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 21:21 [PATCH] Documentation: devicetree: meson-ir: "linux, rc-map-name" is supported Martin Blumenstingl
2017-02-01 17:47 ` Rob Herring
2017-02-01 18:22   ` Andreas Färber
2017-02-01 22:14 ` [PATCH v2] " Martin Blumenstingl
2017-02-01 22:26   ` [PATCH v2] Documentation: devicetree: meson-ir: "linux,rc-map-name" " Martin Blumenstingl
2017-02-01 22:49     ` Sean Young [this message]
2017-02-02 13:04     ` Andreas Färber

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=20170201224957.GA3631@gofer.mess.org \
    --to=sean@mess.org \
    --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).