From: Moritz Fischer <mdf@kernel.org>
To: Alan Tull <atull@kernel.org>
Cc: federico.vaga@cern.ch, linux-fpga@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: fpga: fpga_mgr_free usage
Date: Wed, 11 Jul 2018 11:25:53 -0700 [thread overview]
Message-ID: <20180711182553.GA5356@archbook> (raw)
In-Reply-To: <CANk1AXRewvAAxRi=kmCNL3CEki9ODk7LvLS6q8Hd64JRanyfew@mail.gmail.com>
Hi Alan,
On Wed, Jul 11, 2018 at 10:59:01AM -0500, Alan Tull wrote:
> On Wed, Jul 11, 2018 at 7:38 AM, Federico Vaga <federico.vaga@cern.ch> wrote:
[..]
> > This makes the usage consistent: the user creates and destroy its own
> > objects. This is also consistent with our other discussion where we
> > said, among the other things, that the module that uses the FPGA
> > manager can the owner of the fpga_manager data structure.
>
> You're not the first to complain about this. I think I'll err on the
> side of consistency and implement your option 2 here.
I agree, that seems like a good approach.
Cheers,
Moritz
next prev parent reply other threads:[~2018-07-11 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 12:38 fpga: fpga_mgr_free usage Federico Vaga
2018-07-11 15:59 ` Alan Tull
2018-07-11 18:25 ` Moritz Fischer [this message]
2018-07-25 16:33 ` Alan Tull
2018-07-26 7:27 ` Federico Vaga
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=20180711182553.GA5356@archbook \
--to=mdf@kernel.org \
--cc=atull@kernel.org \
--cc=federico.vaga@cern.ch \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@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