From: Mark Brown <broonie@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: lgirdwood@gmail.com, linux-kernel@vger.kernel.org, phh@phh.me,
b.galvani@gmail.com, stefan@agner.ch
Subject: Re: [PATCH] regulator: rn5t618: fix rc5t619 ldo10 enable
Date: Thu, 14 Nov 2019 19:08:43 +0000 [thread overview]
Message-ID: <20191114190843.GB4664@sirena.co.uk> (raw)
In-Reply-To: <20191114152451.1756b0c8@kemnade.info>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
On Thu, Nov 14, 2019 at 03:24:51PM +0100, Andreas Kemnade wrote:
> Mark Brown <broonie@kernel.org> wrote:
> > On Wed, Nov 13, 2019 at 08:26:33PM +0100, Andreas Kemnade wrote:
> > > Well, it is not just guessing, it is there in the url I referenced. But
> > > I would of course prefer a better source. At first I wanted to spread
> > > my findings.
> > The URL you provided looked to be for a different part though?
> No, they just skip the rc5t in the name. Same situation in the vendor
> kernel for my device, but there is only a tarball online, so it is bad
> to reference. Everything is named there ricoh619 (or 61x). And on the chip is
> printed rc5t619.
Ah, OK - that's probably good enough then. Let's leave it a bit and see
if we can get some more definite review though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-11-14 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 18:26 [PATCH] regulator: rn5t618: fix rc5t619 ldo10 enable Andreas Kemnade
2019-11-13 18:32 ` Mark Brown
2019-11-13 19:26 ` Andreas Kemnade
2019-11-14 11:54 ` Mark Brown
2019-11-14 12:13 ` Stefan Agner
2019-11-14 14:30 ` Andreas Kemnade
2019-11-14 14:24 ` Andreas Kemnade
2019-11-14 19:08 ` Mark Brown [this message]
2019-11-20 7:46 ` Pierre-Hugues Husson
2019-11-20 17:18 ` Applied "regulator: rn5t618: fix rc5t619 ldo10 enable" to the regulator tree Mark Brown
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=20191114190843.GB4664@sirena.co.uk \
--to=broonie@kernel.org \
--cc=andreas@kemnade.info \
--cc=b.galvani@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phh@phh.me \
--cc=stefan@agner.ch \
/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).