From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] clk: meson: gxbb: fix wrong clock for SARADC/SANA
Date: Mon, 06 Nov 2017 10:45:51 +0100 [thread overview]
Message-ID: <1509961551.1328.13.camel@baylibre.com> (raw)
In-Reply-To: <9b1f5cb5-9029-8865-a867-54d819b42e1a@amlogic.com>
On Mon, 2017-11-06 at 17:38 +0800, Yixun Lan wrote:
> > * Is it an error in the published datasheets ?
>
> then, I think the published datasheet need to be updated.
This needs to be clearly explained in your patch description/comment, or maybe
directly in the code.
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Brunet <jbrunet@baylibre.com>
To: Yixun Lan <yixun.lan@amlogic.com>,
Neil Armstrong <narmstrong@baylibre.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Carlo Caione <carlo@caione.org>,
Kevin Hilman <khilman@baylibre.com>,
Xingyu Chen <xingyu.chen@amlogic.com>,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: meson: gxbb: fix wrong clock for SARADC/SANA
Date: Mon, 06 Nov 2017 10:45:51 +0100 [thread overview]
Message-ID: <1509961551.1328.13.camel@baylibre.com> (raw)
In-Reply-To: <9b1f5cb5-9029-8865-a867-54d819b42e1a@amlogic.com>
On Mon, 2017-11-06 at 17:38 +0800, Yixun Lan wrote:
> > * Is it an error in the published datasheets ?
>
> then, I think the published datasheet need to be updated.
This needs to be clearly explained in your patch description/comment, or maybe
directly in the code.
WARNING: multiple messages have this Message-ID (diff)
From: jbrunet@baylibre.com (Jerome Brunet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: meson: gxbb: fix wrong clock for SARADC/SANA
Date: Mon, 06 Nov 2017 10:45:51 +0100 [thread overview]
Message-ID: <1509961551.1328.13.camel@baylibre.com> (raw)
In-Reply-To: <9b1f5cb5-9029-8865-a867-54d819b42e1a@amlogic.com>
On Mon, 2017-11-06 at 17:38 +0800, Yixun Lan wrote:
> > * Is it an error in the published datasheets ?
>
> then, I think the published datasheet need to be updated.
This needs to be clearly explained in your patch description/comment, or maybe
directly in the code.
next prev parent reply other threads:[~2017-11-06 9:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 7:52 [PATCH] clk: meson: gxbb: fix wrong clock for SARADC/SANA Yixun Lan
2017-11-06 7:52 ` Yixun Lan
2017-11-06 7:52 ` Yixun Lan
2017-11-06 8:57 ` Neil Armstrong
2017-11-06 8:57 ` Neil Armstrong
2017-11-06 8:57 ` Neil Armstrong
2017-11-06 9:31 ` Yixun Lan
2017-11-06 9:31 ` Yixun Lan
2017-11-06 9:31 ` Yixun Lan
2017-11-06 22:03 ` Martin Blumenstingl
2017-11-06 22:03 ` Martin Blumenstingl
2017-11-06 22:03 ` Martin Blumenstingl
2017-11-07 5:44 ` Yixun Lan
2017-11-07 5:44 ` Yixun Lan
2017-11-07 5:44 ` Yixun Lan
2017-11-06 9:10 ` Jerome Brunet
2017-11-06 9:10 ` Jerome Brunet
2017-11-06 9:10 ` Jerome Brunet
2017-11-06 9:38 ` Yixun Lan
2017-11-06 9:38 ` Yixun Lan
2017-11-06 9:38 ` Yixun Lan
2017-11-06 9:44 ` Jerome Brunet
2017-11-06 9:44 ` Jerome Brunet
2017-11-06 9:44 ` Jerome Brunet
2017-11-06 9:45 ` Jerome Brunet [this message]
2017-11-06 9:45 ` Jerome Brunet
2017-11-06 9:45 ` Jerome Brunet
2017-11-06 9:51 ` Yixun Lan
2017-11-06 9:51 ` Yixun Lan
2017-11-06 9:51 ` Yixun Lan
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=1509961551.1328.13.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 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.