From: Remi Pommarel <repk@triplefau.lt>
To: Eric Anholt <eric@anholt.net>
Cc: Stefan Wahren <info@lategoodbye.de>,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v3 4/4] clk: bcm2835: Add PWM clock support to the device tree
Date: Wed, 16 Dec 2015 08:57:26 +0100 [thread overview]
Message-ID: <20151216075725.GF453@cruxbox> (raw)
In-Reply-To: <87wpspeg38.fsf@eliezer.anholt.net>
On Mon, Dec 07, 2015 at 08:09:47PM -0800, Eric Anholt wrote:
> Stefan Wahren <info@lategoodbye.de> writes:
>
> > Hi Remi,
> >
> > Am 07.12.2015 um 19:17 schrieb Remi Pommarel:
> >> Hi Stefan,
> >>
> >> On Sun, Dec 06, 2015 at 10:16:25PM +0100, Stefan Wahren wrote:
> >>> Hi Remi,
> >>>
> >>> please send this patch to devicetree@vger.kernel.org.
> >>
> >> Ok, just to be sure I understand the process here. I should resend a new
> >> version of the whole patchset including the devicetree mailing list as
> >> recipent. Then the first 3 patches will eventually get pushed by a clock
> >> subsystem maintainer. And finally this last patch will be pushed by a
> >> devicetree maintainer.
> >>
> >> Am I right here ?
> >
> > sorry for the confusion. I mean that you send a copy to
> > devicetree@vger.kernel.org so subscribers have a chance to review.
> >
> > I'm not sure but according to your subject you suggest that this dts
> > patch should go through clock subsystem which isn't optimal. This should
> > be better applied by Stephen or Eric.
>
> It would be applied by me, but that's for me to worry about, not the
> patch submitter. The subject prefix would be "ARM: bcm2835: ", but
> that's trivial for me to fix when applying, not the kind of thing worth
> asking for a respin for.
Thanks for review.
I'll submit dt patch to devicetree@vger.kernel.org for review. Is it better
to submit the whole patchset (patch 1 to 4) to provide some context for the
device tree patch or just this patch alone ?
Best Regards,
--
Remi
next prev parent reply other threads:[~2015-12-16 7:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 16:22 [PATCH v3 0/4] Add PWM clock support for bcm2835 Remi Pommarel
2015-12-06 16:22 ` [PATCH v3 1/4] clk: bcm2835: add a round up ability to the clock divisor Remi Pommarel
2015-12-08 1:28 ` Eric Anholt
2016-01-10 16:27 ` Martin Sperl
2015-12-06 16:22 ` [PATCH v3 2/4] clk: bcm2835: Support for clock parent selection Remi Pommarel
2015-12-08 1:32 ` Eric Anholt
2015-12-06 16:22 ` [PATCH v3 3/4] clk: bcm2835: Add PWM clock support Remi Pommarel
2015-12-06 16:22 ` [PATCH v3 4/4] clk: bcm2835: Add PWM clock support to the device tree Remi Pommarel
2015-12-06 21:16 ` Stefan Wahren
2015-12-07 18:17 ` Remi Pommarel
2015-12-07 18:42 ` Stefan Wahren
2015-12-08 4:09 ` Eric Anholt
2015-12-16 7:57 ` Remi Pommarel [this message]
2015-12-16 20:05 ` Eric Anholt
2015-12-23 18:57 ` [PATCH v3 0/4] Add PWM clock support for bcm2835 Remi Pommarel
2015-12-25 5:06 ` 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=20151216075725.GF453@cruxbox \
--to=repk@triplefau.lt \
--cc=eric@anholt.net \
--cc=info@lategoodbye.de \
--cc=lee@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=swarren@wwwdotorg.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