From: Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Adrian Remonda
<adrianremonda-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"open list:SPI SUBSYSTEM"
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"open list:DOCUMENTATION"
<linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
open list <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] spi: spidev_test: Added functionalities
Date: Sun, 1 Mar 2015 13:39:04 -0700 [thread overview]
Message-ID: <20150301133904.37212fea@lwn.net> (raw)
In-Reply-To: <20150228072742.GM6236-bheZrs9scGb3/WHNxyQH9YN0K6Il/+VY@public.gmane.org>
On Sat, 28 Feb 2015 16:27:42 +0900
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
> > (Meanwhile, I've applied this one).
>
> Sorry, I shoud've been clearer that my previous mail was intended as a
> nack for the patch as submitted - I'd expected SPI documentation/test
> code updates to be going via the SPI tree.
I begin to understand why docs maintainers tend not to hang around for
long :)
I've dropped the commit. In the future I'll ignore patches to
Documentation/spi.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-01 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 19:08 [PATCH] spi: spidev_test: Added functionalities Adrian Remonda
2015-02-26 2:01 ` Mark Brown
2015-02-27 22:11 ` Jonathan Corbet
2015-02-28 7:27 ` Mark Brown
[not found] ` <20150228072742.GM6236-bheZrs9scGb3/WHNxyQH9YN0K6Il/+VY@public.gmane.org>
2015-03-01 20:39 ` Jonathan Corbet [this message]
2015-03-01 18:28 ` AdrianRemonda
2015-03-04 23:54 ` Mark Brown
2015-03-07 17:59 ` AdrianRemonda
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=20150301133904.37212fea@lwn.net \
--to=corbet-t1hc0tsohrs@public.gmane.org \
--cc=adrianremonda-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).