linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Wu, Hao" <hao.wu@intel.com>
To: John Hubbard <jhubbard@nvidia.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: Mon, 25 May 2020 02:25:18 +0000	[thread overview]
Message-ID: <DM6PR11MB38194610D744865657EEB08385B30@DM6PR11MB3819.namprd11.prod.outlook.com> (raw)
In-Reply-To: <ccf86d21-2ecf-7873-1c30-fbea880b9081@nvidia.com>

> >> 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?

Thanks
Hao

> 
> thanks,
> --
> John Hubbard
> NVIDIA

  reply	other threads:[~2020-05-25  2:25 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 [this message]
2020-05-25  2:34         ` John Hubbard

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=DM6PR11MB38194610D744865657EEB08385B30@DM6PR11MB3819.namprd11.prod.outlook.com \
    --to=hao.wu@intel.com \
    --cc=jhubbard@nvidia.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).