From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 0/3] pwm: add pwm AO on meson gx
Date: Thu, 06 Jul 2017 11:02:20 +0200 [thread overview]
Message-ID: <1499331740.15362.11.camel@baylibre.com> (raw)
In-Reply-To: <20170706065910.GJ16144@ulmo.fritz.box>
On Thu, 2017-07-06 at 08:59 +0200, Thierry Reding wrote:
> On Thu, Jun 08, 2017 at 02:24:13PM +0200, Jerome Brunet wrote:
> > The pwms found in the AO domain of the meson gx family have different
> > clock sources than the ones found in the EE domain. The AO pwms only
> > have 2 connected clock input which are clk81 and the crytal.
> >
> > This patchset adds the necessary compatible and the clock data for it.
> >
> > Changes since v1: [0]
> > * Correct clock source order for gxbb pwm ao. Documenation shows xtal as
> > ? source #1 while it is actually source #0
> > * Add patch 3 to fix pwm calculation. Issue while testing pwm with clk81
> > ? as clock source.
> >
> > [0]:??https://lkml.kernel.org/r/20170607133013.4766-1-jbrunet at baylibre.com
> >
> > Jerome Brunet (3):
> > ? dt-bindings: pwm: meson: add comptabible for gxbb ao pwms
> > ? pwm: meson: add compatible for the gxbb ao pwms
> > ? pwm: meson: improve pwm calculation precision.
> >
> > ?.../devicetree/bindings/pwm/pwm-meson.txt??????????|??4 +-
> > ?drivers/pwm/pwm-meson.c????????????????????????????| 47 +++++++++++++++++
> > -----
> > ?2 files changed, 41 insertions(+), 10 deletions(-)
>
> For some reason the Author field keeps getting set to:
>
> jbrunet <jbrunet@baylibre.com>
>
> It seems like the headers are correct, so maybe this is patchwork
> messing things up?
And it strikes again ... :(
I already had the issue with https://patchwork.kernel.org a few month ago.
I have contacted the kernel.org helpdesk about it and here is the explanation:
"Patchwork treats users and patch submitters slightly differently, so once your
entry is created upon first patch submission, it sticks forever. I've adjusted
your entry manually per your request."
So my very first patch on the ML must have been malformed somehow.
>
> Anyway, I've applied the series and manually fixed up the Author field.
Thanks a lot for this !
Any idea who I may contact to get this "manual adjustment" done on https://patch
work.ozlabs.org/ ?
>
> Thanks,
> Thierry
next prev parent reply other threads:[~2017-07-06 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 12:24 [PATCH v2 0/3] pwm: add pwm AO on meson gx Jerome Brunet
2017-06-08 12:24 ` [PATCH v2 1/3] dt-bindings: pwm: meson: add comptabible for gxbb ao pwms Jerome Brunet
2017-06-13 22:18 ` Rob Herring
2017-06-08 12:24 ` [PATCH v2 2/3] pwm: meson: add compatible for the " Jerome Brunet
2017-06-14 17:38 ` Kevin Hilman
2017-06-08 12:24 ` [PATCH v2 3/3] pwm: meson: improve pwm calculation precision Jerome Brunet
2017-06-08 12:35 ` Neil Armstrong
2017-07-06 21:21 ` Thierry Reding
2017-07-07 8:57 ` Jerome Brunet
2017-07-06 6:59 ` [PATCH v2 0/3] pwm: add pwm AO on meson gx Thierry Reding
2017-07-06 9:02 ` Jerome Brunet [this message]
2017-07-06 9:17 ` Thierry Reding
2017-07-14 5:51 ` Jeremy Kerr
2017-07-18 14:52 ` Thierry Reding
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=1499331740.15362.11.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus-amlogic@lists.infradead.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).