linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Ford <aford173@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add logicpd-som-lv and logicpd-torpedo to OMAP TREE
Date: Mon, 21 Oct 2019 16:40:52 -0500	[thread overview]
Message-ID: <CAHCN7xLQvYbY_Pu5hQOO8o+1o8CAVvXq_-RM78Q=jYvtLxtmbg@mail.gmail.com> (raw)
In-Reply-To: <20190923135908.23080-1-aford173@gmail.com>

On Mon, Sep 23, 2019 at 8:59 AM Adam Ford <aford173@gmail.com> wrote:
>
> The OMAP DEVICE TREE SUPPORT lists a bunch of device tree files
> with wildcard names using am3*, am4*, am5*, dra7*, and *omap*.
> Unfortunately, the LogicPD boards do not follow this convention
> so changes to these boards don't get automatically flagged to
> route to the omap mailing list.  After consulting with Tony
> Lindgren, he agreed it made sense to add these boards to the
> list.
>
> This patch adds the omap based boards to the omap device tree
> maintainer list.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>

Tony,

Are you ok with this?  I am not sure who to bug, but I am guessing
whomever it is will want/need your approval too.

adam
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a50e97a63bc8..0ee89575699c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11645,6 +11645,8 @@ F:      arch/arm/boot/dts/*am3*
>  F:     arch/arm/boot/dts/*am4*
>  F:     arch/arm/boot/dts/*am5*
>  F:     arch/arm/boot/dts/*dra7*
> +F:     arch/arm/boot/dts/logicpd-som-lv*
> +F:     arch/arm/boot/dts/logicpd-torpedo*
>
>  OMAP DISPLAY SUBSYSTEM and FRAMEBUFFER SUPPORT (DSS2)
>  L:     linux-omap@vger.kernel.org
> --
> 2.17.1
>

  parent reply	other threads:[~2019-10-21 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23 13:59 [PATCH] MAINTAINERS: Add logicpd-som-lv and logicpd-torpedo to OMAP TREE Adam Ford
2019-09-23 13:59 ` Adam Ford
2019-09-23 13:59 ` Adam Ford
2019-10-21 21:40 ` Adam Ford [this message]
2019-10-22 16:03   ` Tony Lindgren

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='CAHCN7xLQvYbY_Pu5hQOO8o+1o8CAVvXq_-RM78Q=jYvtLxtmbg@mail.gmail.com' \
    --to=aford173@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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).