From: Mark Brown <broonie@kernel.org>
To: Ben Whitten <ben.whitten@gmail.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Add ability to multiplex SPI bus
Date: Tue, 23 Jan 2018 10:46:55 +0000 [thread overview]
Message-ID: <20180123104655.GA7600@sirena.org.uk> (raw)
In-Reply-To: <1516661472-16452-1-git-send-email-ben.whitten@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
On Mon, Jan 22, 2018 at 10:51:11PM +0000, Ben Whitten wrote:
> A chip that I am working on acts as an SPI multiplexer for downstream radios,
> this patch adds basic support for adding an SPI mux with DT.
Please don't send cover letters for single patches, if there is anything
that needs saying put it in the changelog of the patch or after the ---
if it's administrative stuff. This reduces mail volume and ensures that
any important information is recorded in the changelog rather than being
lost.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-01-23 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 22:51 [RFC] Add ability to multiplex SPI bus Ben Whitten
[not found] ` <1516661472-16452-1-git-send-email-ben.whitten-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-22 22:51 ` [RFC] spi: add spi multiplexing functions for dt Ben Whitten
[not found] ` <1516661472-16452-2-git-send-email-ben.whitten-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-23 11:11 ` Mark Brown
[not found] ` <20180123111123.GB7600-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2018-01-24 14:01 ` Ben Whitten
[not found] ` <CAF3==it=5_YQVJ9xg8CLzSPw7LQZbCHQHfsufYwwCb=n7x3L0g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-24 14:54 ` Mark Brown
[not found] ` <20180124145430.GD9366-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2018-01-25 15:54 ` Ben Whitten
2018-01-23 10:46 ` Mark Brown [this message]
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=20180123104655.GA7600@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ben.whitten@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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).