From: AdrianRemonda <adrianremonda@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
"open list:SPI SUBSYSTEM" <linux-spi@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi: spidev_test: Added functionalities
Date: Sat, 7 Mar 2015 12:59:24 -0500 [thread overview]
Message-ID: <20150307175924.GA18227@debian> (raw)
In-Reply-To: <20150304235439.GX21293@sirena.org.uk>
On Wed, Mar 04, 2015 at 11:54:39PM +0000, Mark Brown wrote:
> On Sun, Mar 01, 2015 at 07:28:41PM +0100, AdrianRemonda wrote:
>
> > I apologize for the wrong patch format.
> > Should I contact the mantainer of the tool path and ask him where to add
> > it? Or how should I proceed?
>
> I am the relevant maintainer here. The main thing from my point of view
> is to split the three changes you were making out into separate commits
> so they can be easily reviewed. Jon is right that this should be moved
> into a better directory but that's a separate issue that can be tackled
> separately (though feel free to do it immediately if you like!).
Thanks. I sent it to you and moved it to the tools dir.
Regards,
Adrian
prev parent reply other threads:[~2015-03-07 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 19:08 [PATCH] spi: spidev_test: Added functionalities Adrian Remonda
2015-02-25 19:08 ` 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
2015-03-01 20:39 ` Jonathan Corbet
2015-03-01 18:28 ` AdrianRemonda
2015-03-04 23:54 ` Mark Brown
2015-03-07 17:59 ` AdrianRemonda [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=20150307175924.GA18227@debian \
--to=adrianremonda@gmail.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--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 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.