From: Anatolij Gustschin <agust@denx.de>
To: Alan Tull <atull@kernel.org>
Cc: linux-fpga@vger.kernel.org, Moritz Fischer <mdf@kernel.org>
Subject: Re: [PATCH v2] fpga: mgr: add notifier for manager register/unregister events
Date: Tue, 6 Nov 2018 10:29:31 +0100 [thread overview]
Message-ID: <20181106102931.7ec6d038@crub> (raw)
In-Reply-To: <CANk1AXTTWMSsnjSgubnP6Mrt5GJ_edOL=cgix_rcrXs7t4-2CA@mail.gmail.com>
Hi Alan,
On Mon, 5 Nov 2018 15:08:03 -0600
Alan Tull atull@kernel.org wrote:
>On Mon, Nov 5, 2018 at 11:15 AM Anatolij Gustschin <agust@denx.de> wrote:
>
>Hi Anatolij,
>
>>
>> Add API functions for registering and removing a notifier for FPGA
>> manager register/unregister events. Notify when a new FPGA manager
>> has been registered or when an existing manager is being removed.
>> This will help configuration interface drivers to get the notion
>> of low-level FPGA managers appearing or disappearing, when using
>> hotpluggable FPGA configuration devices (e.g. via USB-FPP or
>> USB-SPI adapters).
>
>Are you going to be adding any code upstream that uses this API?
I'd like to add our fpga-cfg driver [1] in upstream which uses this API.
Here [2] is a better readable README about it.
Thanks,
Anatolij
[1] http://git.denx.de/?p=fpga-cfg.git;a=summary
[2] https://github.com/vdsao/fpga-cfg/blob/master/README.md
next prev parent reply other threads:[~2018-11-06 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 17:14 [PATCH v2] fpga: mgr: add notifier for manager register/unregister events Anatolij Gustschin
2018-11-05 21:08 ` Alan Tull
2018-11-06 9:29 ` Anatolij Gustschin [this message]
2018-11-06 17:22 ` Alan Tull
2018-11-06 19:47 ` Alan Tull
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=20181106102931.7ec6d038@crub \
--to=agust@denx.de \
--cc=atull@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=mdf@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).