From: Alan Tull <atull@kernel.org>
To: Moritz Fischer <moritz.fischer.private@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
Federico Vaga <federico.vaga@cern.ch>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fpga@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v3 4/4] docs: fpga: document programming fpgas using regions
Date: Mon, 15 Oct 2018 15:40:08 -0500 [thread overview]
Message-ID: <CANk1AXQxX8_AMkJhSbuNgxb1972dRqv-6niqU3V63FzKE8=wtQ@mail.gmail.com> (raw)
In-Reply-To: <CAJYdmeNdBbJBVGjLkk03PpGERA2j=D__BVsb9_FBXwWFkMXR_Q@mail.gmail.com>
On Mon, Oct 15, 2018 at 3:11 PM Moritz Fischer
<moritz.fischer.private@gmail.com> wrote:
>
> On Wed, Sep 26, 2018 at 9:12 AM Alan Tull <atull@kernel.org> wrote:
> >
> > Clarify the intention that interfaces and upper layers use
> > regions rather than managers directly.
> >
> > Rearrange API documentation to better group the API functions
> > used to create FPGA mgr/bridge/regions and the API used for
> > programming FPGAs.
> >
> > Signed-off-by: Alan Tull <atull@kernel.org>
> > Suggested-by: Federico Vaga <federico.vaga@cern.ch>
>
> Acked-by: Moritz Fischer <mdf@kernel.org>
Thanks Moritz!
Alan
prev parent reply other threads:[~2018-10-15 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 16:12 [PATCH v3 0/4] fpga: add devm managed create APIs Alan Tull
2018-09-26 16:12 ` [PATCH v3 1/4] fpga: mgr: add devm_fpga_mgr_create Alan Tull
2018-10-15 14:54 ` Alan Tull
2018-10-15 17:32 ` Moritz Fischer
2018-10-16 7:02 ` Federico Vaga
2018-10-16 7:02 ` Federico Vaga
2018-09-26 16:12 ` [PATCH v3 2/4] fpga: bridge: add devm_fpga_bridge_create Alan Tull
2018-09-26 16:49 ` Eric.Delage
2018-09-26 20:13 ` Alan Tull
2018-09-26 20:31 ` Eric.Delage
2018-09-26 16:12 ` [PATCH v3 3/4] fpga: add devm_fpga_region_create Alan Tull
2018-10-15 20:10 ` Moritz Fischer
2018-09-26 16:12 ` [PATCH v3 4/4] docs: fpga: document programming fpgas using regions Alan Tull
2018-10-15 20:11 ` Moritz Fischer
2018-10-15 20:40 ` Alan Tull [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='CANk1AXQxX8_AMkJhSbuNgxb1972dRqv-6niqU3V63FzKE8=wtQ@mail.gmail.com' \
--to=atull@kernel.org \
--cc=corbet@lwn.net \
--cc=federico.vaga@cern.ch \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moritz.fischer.private@gmail.com \
--cc=rdunlap@infradead.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.