linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] MAINTAINERS: catch special Rockchip code locations
Date: Wed, 27 Aug 2014 15:13:06 -0700	[thread overview]
Message-ID: <20140827221306.GD13392@localhost> (raw)
In-Reply-To: <3644024.F4LLe7dWA4@diego>

On Wed, Aug 27, 2014 at 12:05:50AM +0200, Heiko St?bner wrote:
> Add some more locations that aren't catched by the general wildcard.
> This includes the devicetree files, clock directory, rk3x i2c driver,
> everything in a third layer under drivers like iio/adc/rockchip_saradc.c
> and the i2s driver.
> 
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
> Main reason behind this, is that I only accidentially stumbled over the
> clock api refactoring series [0] from Toneu Vizoso, wheras with the
> better matching it should've been automatic.
> 
> [0] https://lkml.org/lkml/2014/8/18/481

Applied for 3.17.


Thanks,

-Olof

      reply	other threads:[~2014-08-27 22:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 22:05 [PATCH RESEND] MAINTAINERS: catch special Rockchip code locations Heiko Stübner
2014-08-27 22:13 ` Olof Johansson [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=20140827221306.GD13392@localhost \
    --to=olof@lixom.net \
    --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).