From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Mark Brown <broonie@kernel.org>
Cc: "linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
"hsweeten@visionengravers.com" <hsweeten@visionengravers.com>
Subject: Re: [PATCH v2 1/7] spi: spi-ep93xx: remove io wrappers
Date: Tue, 8 Aug 2017 20:43:48 +0000 [thread overview]
Message-ID: <284dbb1bcf3043caa5da5019f0cc4914@svr-chch-ex1.atlnz.lc> (raw)
In-Reply-To: 20170808094236.l5dnyrlh4sqybaqg@sirena.org.uk
On 08/08/17 21:42, Mark Brown wrote:
> On Fri, Aug 04, 2017 at 12:00:17PM +1200, Chris Packham wrote:
>> From: H Hartley Sweeten <hsweeten@visionengravers.com>
>>
>> The io wrappers just add obfuscation to the driver. Remove them.
>>
>> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
>> ---
>
> I can't do anything with this patch since you haven't provided a signoff
> - this is essential for anything going upstream, please see
> SubmittingPatches for detais on what it means and why it's important.
>
I didn't sign it because it's the patch that came from Hartley verbatim
(same for 5/7, 6/7 and 7/7). The ones I did sign I'd made changes to.
Re-reading the DCO point c I understand now that I should have signed
all of them so I'll submit a v3 series to do so.
next prev parent reply other threads:[~2017-08-08 20:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 0:00 [PATCH v2 0/7] spi: spi-ep93xx: cleanup and update driver to modern API Chris Packham
2017-08-04 0:00 ` [PATCH v2 1/7] spi: spi-ep93xx: remove io wrappers Chris Packham
2017-08-08 9:42 ` Mark Brown
2017-08-08 20:43 ` Chris Packham [this message]
2017-08-04 0:00 ` [PATCH v2 2/7] spi: spi-ep93xx: use 32-bit read/write for all registers Chris Packham
2017-08-09 16:57 ` Applied "spi: spi-ep93xx: use 32-bit read/write for all registers" to the spi tree Mark Brown
2017-08-04 0:00 ` [PATCH v2 3/7] spi: spi-ep93xx: add spi master prepare_transfer_hardware() Chris Packham
2017-08-09 16:57 ` Applied "spi: spi-ep93xx: add spi master prepare_transfer_hardware()" to the spi tree Mark Brown
2017-08-04 0:00 ` [PATCH v2 4/7] spi: spi-ep93xx: absorb the interrupt enable/disable helpers Chris Packham
2017-08-09 16:57 ` Applied "spi: spi-ep93xx: absorb the interrupt enable/disable helpers" to the spi tree Mark Brown
2017-08-04 0:00 ` [PATCH v2 5/7] spi: spi-ep93xx: pass the spi_master pointer around Chris Packham
2017-08-09 16:57 ` Applied "spi: spi-ep93xx: pass the spi_master pointer around" to the spi tree Mark Brown
2017-08-04 0:00 ` [PATCH v2 6/7] spi: spi-ep93xx: remove private data 'current_msg' Chris Packham
2017-08-04 0:00 ` [PATCH v2 7/7] spi: spi-ep93xx: use the default master transfer queueing mechanism Chris Packham
2017-08-09 16:56 ` Applied "spi: spi-ep93xx: use the default master transfer queueing mechanism" to the spi 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=284dbb1bcf3043caa5da5019f0cc4914@svr-chch-ex1.atlnz.lc \
--to=chris.packham@alliedtelesis.co.nz \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=hsweeten@visionengravers.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).