From: Daniel Palmer <daniel@0x0f.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: linux-iio <linux-iio@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [RFC PATCH 2/2] iio: st-accel: Add support for Silan SC7A20 and SC7A30E
Date: Sun, 16 Aug 2020 20:59:57 +0900 [thread overview]
Message-ID: <CAFr9PXma7_FUVZbGk7kzfc1xgYH8WdMWj6FZuO4wO=kNp=iR-w@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VcreDeik-pCQPXV2RQVAEPFNRjGS8Mutvxwog1khVka4g@mail.gmail.com>
Hi Andy,
On Sun, 16 Aug 2020 at 18:55, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> No SoB tag?! Hint: `git commit -a -s --amend` would fix this if you
> have properly configured Git.
>
Sorry I wasn't aware it was needed for an RFC.
> On top of that, can you add Datasheet: tag with links to the actual
> component datasheets?
I will do that for the v1 of the patch series. All of the datasheets
I've found so far are mostly Chinese
but the register tables are in English. I've collected them together
here: http://linux-chenxing.org/silan/index.html
Cheers,
Daniel
next prev parent reply other threads:[~2020-08-16 12:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 13:48 [RFC PATCH 0/2] iio: st-accel: Add support for Silan clones Daniel Palmer
2020-08-11 13:48 ` [RFC PATCH 1/2] dt-bindings: vendor-prefixes: Add vendor prefix for Silan Daniel Palmer
2020-08-16 8:50 ` Jonathan Cameron
2020-08-11 13:48 ` [RFC PATCH 2/2] iio: st-accel: Add support for Silan SC7A20 and SC7A30E Daniel Palmer
2020-08-16 8:52 ` Jonathan Cameron
2020-08-16 9:27 ` Daniel Palmer
2020-08-16 9:40 ` Jonathan Cameron
2020-08-16 9:55 ` Andy Shevchenko
2020-08-16 11:59 ` Daniel Palmer [this message]
2020-08-19 18:19 ` Denis CIOCCA
2020-08-20 9:01 ` Jonathan Cameron
2020-08-20 9:17 ` Greg KH
2020-08-20 12:27 ` Daniel Palmer
2020-08-20 12:56 ` Andy Shevchenko
2020-08-20 12:34 ` Andy Shevchenko
2020-08-12 9:20 ` [RFC PATCH 0/2] iio: st-accel: Add support for Silan clones Jonathan Cameron
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='CAFr9PXma7_FUVZbGk7kzfc1xgYH8WdMWj6FZuO4wO=kNp=iR-w@mail.gmail.com' \
--to=daniel@0x0f.com \
--cc=andy.shevchenko@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.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).