From: Alan Tull <atull@kernel.org>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: atull <atull@opensource.altera.com>,
Moritz Fischer <moritz.fischer@ettus.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fpga@vger.kernel.org
Subject: Re: [PATCH v3 fpga 3/4] fpga: Add scatterlist based programming
Date: Mon, 9 Jan 2017 16:13:38 -0600 [thread overview]
Message-ID: <CANk1AXTrB3Rvxn1vvNYFGz0N8+w5wDR8SYJFEmwaMicvJN=O8A@mail.gmail.com> (raw)
In-Reply-To: <20170109161204.GA28149@obsidianresearch.com>
On Mon, Jan 9, 2017 at 10:12 AM, Jason Gunthorpe
<jgunthorpe@obsidianresearch.com> wrote:
> On Mon, Jan 09, 2017 at 10:04:36AM -0600, Alan Tull wrote:
>
>> > diff --git a/drivers/fpga/fpga-mgr.c b/drivers/fpga/fpga-mgr.c
>> > index f0a69d3e60a584..30f9778d0632d2 100644
>> > +++ b/drivers/fpga/fpga-mgr.c
>> > @@ -1,4 +1,4 @@
>> > -/*
>> > + /*
>>
>> Hi Jason,
>>
>> Need to take these added 2 spaces out. Otherwise,
>
> Huh, where did those come from - can you drop that hunk when you apply
> it to your tree?
I'm not going to be applying to a tree and doing pull requests. Greg
wants to take patches straight from the mailing list.
Alan
>
> Thanks,
> Jason
next prev parent reply other threads:[~2017-01-09 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 21:14 [PATCH v3 fpga 0/4] Zynq FPGA dma patches Jason Gunthorpe
2017-01-06 21:14 ` [PATCH v3 fpga 1/4] fpga zynq: Check for errors after completing DMA Jason Gunthorpe
2017-01-06 21:14 ` [PATCH v3 fpga 2/4] fpga zynq: Check the bitstream for validity Jason Gunthorpe
2017-01-06 21:14 ` [PATCH v3 fpga 3/4] fpga: Add scatterlist based programming Jason Gunthorpe
2017-01-09 16:04 ` Alan Tull
2017-01-09 16:12 ` Jason Gunthorpe
2017-01-09 22:13 ` Alan Tull [this message]
2017-01-27 21:58 ` Jason Gunthorpe
2017-01-28 10:36 ` Moritz Fischer
2017-01-06 21:14 ` [PATCH v3 fpga 4/4] fpga zynq: Use the scatterlist interface Jason Gunthorpe
2017-01-28 10:33 ` Moritz Fischer
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='CANk1AXTrB3Rvxn1vvNYFGz0N8+w5wDR8SYJFEmwaMicvJN=O8A@mail.gmail.com' \
--to=atull@kernel.org \
--cc=atull@opensource.altera.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moritz.fischer@ettus.com \
/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).