From: Stephen Boyd <sboyd@codeaurora.org>
To: Paul Walmsley <paul@pwsan.com>
Cc: Mike Turquette <mturquette@linaro.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Viresh Kumar <viresh.linux@gmail.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Tero Kristo <t-kristo@ti.com>,
Russell King <linux@arm.linux.org.uk>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: clk: discuss on the linux-clk@vger.kernel.org list
Date: Fri, 27 Mar 2015 00:17:59 -0700 [thread overview]
Message-ID: <20150327071759.GA18059@codeaurora.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1503251828240.13341@utopia.booyaka.com>
On 03/25, Paul Walmsley wrote:
>
> Most Linux clock framework discussions take place on the
> linux-kernel@vger.kernel.org or linux-arm-kernel@lists.infradead.org
> mailing lists. The volume of unrelated messages on these lists makes
> it difficult for non-maintainers to follow along with discussions.
> Switch the discussion list for clock framework discussions to
> linux-clk@vger.kernel.org. Also, add linux-clk@vger.kernel.org as a
> mailing list for clock API discussions.
>
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> Cc: Mike Turquette <mturquette@linaro.org>
> Cc: Stephen Boyd <sboyd@codeaurora.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
> Cc: Tomasz Figa <tomasz.figa@gmail.com>
> Cc: Viresh Kumar <viresh.linux@gmail.com>
> Cc: Peter De Schrijver <pdeschrijver@nvidia.com>
> Cc: Prashant Gaikwad <pgaikwad@nvidia.com>
> Cc: Tero Kristo <t-kristo@ti.com>
> Cc: Russell King <linux@arm.linux.org.uk>
> ---
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
Mike or I will pick this up for 4.1
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: clk: discuss on the linux-clk@vger.kernel.org list
Date: Fri, 27 Mar 2015 00:17:59 -0700 [thread overview]
Message-ID: <20150327071759.GA18059@codeaurora.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1503251828240.13341@utopia.booyaka.com>
On 03/25, Paul Walmsley wrote:
>
> Most Linux clock framework discussions take place on the
> linux-kernel at vger.kernel.org or linux-arm-kernel at lists.infradead.org
> mailing lists. The volume of unrelated messages on these lists makes
> it difficult for non-maintainers to follow along with discussions.
> Switch the discussion list for clock framework discussions to
> linux-clk at vger.kernel.org. Also, add linux-clk at vger.kernel.org as a
> mailing list for clock API discussions.
>
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> Cc: Mike Turquette <mturquette@linaro.org>
> Cc: Stephen Boyd <sboyd@codeaurora.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
> Cc: Tomasz Figa <tomasz.figa@gmail.com>
> Cc: Viresh Kumar <viresh.linux@gmail.com>
> Cc: Peter De Schrijver <pdeschrijver@nvidia.com>
> Cc: Prashant Gaikwad <pgaikwad@nvidia.com>
> Cc: Tero Kristo <t-kristo@ti.com>
> Cc: Russell King <linux@arm.linux.org.uk>
> ---
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
Mike or I will pick this up for 4.1
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-03-27 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 18:32 [PATCH] MAINTAINERS: clk: discuss on the linux-clk@vger.kernel.org list Paul Walmsley
2015-03-25 18:32 ` Paul Walmsley
2015-03-27 7:17 ` Stephen Boyd [this message]
2015-03-27 7:17 ` Stephen Boyd
2015-04-01 1:36 ` Michael Turquette
2015-04-01 1:36 ` Michael Turquette
2015-04-01 1:36 ` Michael Turquette
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=20150327071759.GA18059@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@linaro.org \
--cc=paul@pwsan.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=s.nawrocki@samsung.com \
--cc=t-kristo@ti.com \
--cc=tglx@linutronix.de \
--cc=tomasz.figa@gmail.com \
--cc=viresh.linux@gmail.com \
/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.