From: Moritz Fischer <mdf@kernel.org>
To: Russ Weight <russell.h.weight@intel.com>
Cc: mdf@kernel.org, linux-fpga@vger.kernel.org, trix@redhat.com,
lgoncalv@redhat.com, yilun.xu@intel.com, hao.wu@intel.com,
matthew.gerlach@intel.com, richard.gong@intel.com
Subject: Re: [RESEND PATCH v10 0/3] fpga: Use standard class dev_release function
Date: Mon, 26 Jul 2021 22:43:19 -0700 [thread overview]
Message-ID: <YP+c98m5AhrGQWDe@epycbox.lan> (raw)
In-Reply-To: <39607b02-bad3-0f65-c1c8-efd6036ab4f3@intel.com>
Hi Russ,
On Mon, Jul 26, 2021 at 02:33:29PM -0700, Russ Weight wrote:
> Hi Moritz,
>
> I sent this version of the patchset out on July 8th. The only discussion has
> been around the compat-id structure. I think there is agreement that this can
> be treated separately. What are your thoughts? Do you think this patchset is
> ready?
It generally looks good. Let's take another look once Greg pulled in the
changes (since there'll also be the new Versal driver and Tom's changes).
- Moritz
next prev parent reply other threads:[~2021-07-27 5:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 21:27 [RESEND PATCH v10 0/3] fpga: Use standard class dev_release function Russ Weight
2021-07-26 21:27 ` [RESEND PATCH v10 1/3] fpga: mgr: Use standard dev_release for class driver Russ Weight
2021-07-26 21:27 ` [RESEND PATCH v10 2/3] fpga: bridge: " Russ Weight
2021-07-26 21:27 ` [RESEND PATCH v10 3/3] fpga: region: " Russ Weight
2021-07-26 21:33 ` [RESEND PATCH v10 0/3] fpga: Use standard class dev_release function Russ Weight
2021-07-27 5:43 ` Moritz Fischer [this message]
2021-07-27 13:24 ` Tom Rix
2021-07-27 16:15 ` Russ Weight
2021-07-27 16:22 ` Tom Rix
2021-07-27 16:38 ` Russ Weight
2021-07-27 16:55 ` Tom Rix
2021-07-27 17:16 ` Russ Weight
2021-07-27 17:44 ` Tom Rix
2021-07-27 21:07 ` Russ Weight
2021-07-28 1:33 ` Xu Yilun
2021-08-20 14:59 ` Tom Rix
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=YP+c98m5AhrGQWDe@epycbox.lan \
--to=mdf@kernel.org \
--cc=hao.wu@intel.com \
--cc=lgoncalv@redhat.com \
--cc=linux-fpga@vger.kernel.org \
--cc=matthew.gerlach@intel.com \
--cc=richard.gong@intel.com \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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).