All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Kukjin Kim <kgene@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] MAINTAINERS: Extend Samsung SoC entry with S3C/S5P drivers
Date: Wed, 22 Jun 2016 21:16:04 +0530	[thread overview]
Message-ID: <20160622154604.GH5458@vireshk-i7> (raw)
In-Reply-To: <1466597805-31988-1-git-send-email-k.kozlowski@samsung.com>

On 22-06-16, 14:16, Krzysztof Kozlowski wrote:
> Some of the drivers for S3C and S5P families of Samsung SoCs go in
> through Samsung SoC tree.  Extend the entry so proper maintainers would
> be displayed in such cases, most notably the cpufreq drivers.  This does
> not change the work-flow for other drivers which have sub-maintainers
> (like Samsung clocks).
> 
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Cc: Kukjin Kim <kgene@kernel.org>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> Cc: linux-samsung-soc@vger.kernel.org
> Cc: linux-pm@vger.kernel.org
> ---
>  MAINTAINERS | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 092ce3990541..1e5cf07030ae 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1619,8 +1619,10 @@ F:	arch/arm/mach-s3c24*/
>  F:	arch/arm/mach-s3c64xx/
>  F:	arch/arm/mach-s5p*/
>  F:	arch/arm/mach-exynos*/
> -F:	drivers/*/*s3c2410*
> -F:	drivers/*/*/*s3c2410*
> +F:	drivers/*/*s3c24*
> +F:	drivers/*/*/*s3c24*
> +F:	drivers/*/*s3c64xx*
> +F:	drivers/*/*s5pv210*
>  F:	drivers/memory/samsung/*
>  F:	drivers/soc/samsung/*
>  F:	drivers/spi/spi-s3c*

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

-- 
viresh

WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Extend Samsung SoC entry with S3C/S5P drivers
Date: Wed, 22 Jun 2016 21:16:04 +0530	[thread overview]
Message-ID: <20160622154604.GH5458@vireshk-i7> (raw)
In-Reply-To: <1466597805-31988-1-git-send-email-k.kozlowski@samsung.com>

On 22-06-16, 14:16, Krzysztof Kozlowski wrote:
> Some of the drivers for S3C and S5P families of Samsung SoCs go in
> through Samsung SoC tree.  Extend the entry so proper maintainers would
> be displayed in such cases, most notably the cpufreq drivers.  This does
> not change the work-flow for other drivers which have sub-maintainers
> (like Samsung clocks).
> 
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Cc: Kukjin Kim <kgene@kernel.org>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> Cc: linux-samsung-soc at vger.kernel.org
> Cc: linux-pm at vger.kernel.org
> ---
>  MAINTAINERS | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 092ce3990541..1e5cf07030ae 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1619,8 +1619,10 @@ F:	arch/arm/mach-s3c24*/
>  F:	arch/arm/mach-s3c64xx/
>  F:	arch/arm/mach-s5p*/
>  F:	arch/arm/mach-exynos*/
> -F:	drivers/*/*s3c2410*
> -F:	drivers/*/*/*s3c2410*
> +F:	drivers/*/*s3c24*
> +F:	drivers/*/*/*s3c24*
> +F:	drivers/*/*s3c64xx*
> +F:	drivers/*/*s5pv210*
>  F:	drivers/memory/samsung/*
>  F:	drivers/soc/samsung/*
>  F:	drivers/spi/spi-s3c*

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

-- 
viresh

  reply	other threads:[~2016-06-22 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 12:16 [PATCH] MAINTAINERS: Extend Samsung SoC entry with S3C/S5P drivers Krzysztof Kozlowski
2016-06-22 12:16 ` Krzysztof Kozlowski
2016-06-22 15:46 ` Viresh Kumar [this message]
2016-06-22 15:46   ` Viresh Kumar

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=20160622154604.GH5458@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.