From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
linux-renesas-soc@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
sakari.ailus@iki.fi
Cc: "Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Jacopo Mondi" <jacopo@jmondi.org>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Subject: Re: [PATCH] MAINTAINERS: Fix sort order for RDACM20
Date: Fri, 28 Aug 2020 10:57:11 +0100 [thread overview]
Message-ID: <bc0882a9-0479-acd9-1a3f-af286b9c8314@ideasonboard.com> (raw)
In-Reply-To: <20200716102552.1390223-1-kieran.bingham+renesas@ideasonboard.com>
Hi Mauro,
I see the fixes branch is open now ... could you pick this one up
please? Or do I need to send a pull request?
--
Regards
Kieran
On 16/07/2020 11:25, Kieran Bingham wrote:
> The files maintained as part of the RDACM20 were incorrectly sorted
> while they were added.
>
> Correct the sort-order.
>
> Fixes: 874a93adf972 ("media: i2c: Add RDACM20 driver")
> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 373e4198d2b1..8bd8d4ab8b5f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14412,9 +14412,9 @@ M: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> L: linux-media@vger.kernel.org
> S: Maintained
> F: Documentation/devicetree/bindings/media/i2c/imi,rdacm2x-gmsl.yaml
> -F: drivers/media/i2c/rdacm20.c
> F: drivers/media/i2c/max9271.c
> F: drivers/media/i2c/max9271.h
> +F: drivers/media/i2c/rdacm20.c
>
> RDC R-321X SoC
> M: Florian Fainelli <florian@openwrt.org>
>
--
Regards
--
Kieran
next prev parent reply other threads:[~2020-08-28 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 10:25 [PATCH] MAINTAINERS: Fix sort order for RDACM20 Kieran Bingham
2020-07-16 10:37 ` Jacopo Mondi
2020-08-28 9:57 ` Kieran Bingham [this message]
2020-08-28 10:56 ` Mauro Carvalho Chehab
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=bc0882a9-0479-acd9-1a3f-af286b9c8314@ideasonboard.com \
--to=kieran.bingham@ideasonboard.com \
--cc=jacopo@jmondi.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=sakari.ailus@iki.fi \
/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).