From: John Hubbard <jhubbard@nvidia.com>
To: "Wu, Hao" <hao.wu@intel.com>, Moritz Fischer <mdf@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Xu, Yilun" <yilun.xu@intel.com>,
"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>
Subject: Re: [PATCH v2] fpga: dfl: afu: convert get_user_pages() --> pin_user_pages()
Date: Sun, 24 May 2020 19:34:35 -0700 [thread overview]
Message-ID: <4f326d89-d034-72ea-06d0-a2f9ba62bcc9@nvidia.com> (raw)
In-Reply-To: <DM6PR11MB38194610D744865657EEB08385B30@DM6PR11MB3819.namprd11.prod.outlook.com>
On 2020-05-24 19:25, Wu, Hao wrote:
>>>> Hi Moritz and FPGA developers,
>>>>
>>>> Is this OK? And if so, is it going into your git tree? Or should I
>>>> send it up through a different tree? (I'm new to the FPGA development
>>>> model).
>>>
>>> I can take it, sorry for sluggish response.
>>>
>>
>> That's great news, thanks Moritz! Sorry to be pushy, just didn't want it
>> to get lost. :)
>
> Thanks John for this patch, and thanks Moritz for taking care of this.
> Sorry for late response, one thing here we may need to be careful is
> a recent bug fixing patch, that fixing patch has been merged by Greg
> in char-misc-next tree, and may have some conflict with this one.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/commit/?h=char-misc-next&id=c9d7e3da1f3c4cf5dddfc5d7ce4d76d013aba1cc
> fpga: dfl: afu: Corrected error handling levels
>
> I guess we need to rebase this patch on top of it?
> Moritz, do you have any suggestion?
>
I'll send you a v2, rebased on top of the latest char-misc.git, no problem.
thanks,
--
John Hubbard
NVIDIA
prev parent reply other threads:[~2020-05-25 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 20:14 [PATCH v2] fpga: dfl: afu: convert get_user_pages() --> pin_user_pages() John Hubbard
2020-05-23 1:52 ` John Hubbard
2020-05-23 20:57 ` Moritz Fischer
2020-05-23 21:33 ` John Hubbard
2020-05-25 2:25 ` Wu, Hao
2020-05-25 2:34 ` John Hubbard [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=4f326d89-d034-72ea-06d0-a2f9ba62bcc9@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--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).