linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wu Hao <hao.wu@intel.com>
To: Will Deacon <will@kernel.org>
Cc: mdf@kernel.org, mark.rutland@arm.com, linux-fpga@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	atull@kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH v6 0/2] add performance reporting support to FPGA DFL drivers
Date: Mon, 25 Nov 2019 16:08:39 +0800	[thread overview]
Message-ID: <20191125080839.GA6227@hao-dev> (raw)
In-Reply-To: <20191125080127.GC1809@willie-the-truck>

On Mon, Nov 25, 2019 at 08:01:28AM +0000, Will Deacon wrote:
> On Mon, Nov 25, 2019 at 11:34:12AM +0800, Wu Hao wrote:
> > Hi Will and Mark,
> > 
> > Could you please help us on review this patchset? as this patchset mainly 
> > introduced a new perf driver following the similar way as drivers/perf/*.
> 
> Why is it not under drivers/perf/, then?

Hi Will

Thanks for the quick response. This is one sub feature for DFL based FPGAs,
and we plan to put this sub feature together with others, including related
documentation. It only registers a standard perf pmu for its userspace
interfaces.

> 
> > This patchset has been submitted for a long time but didn't receive any
> > comment after v4. we appreciate any review comments! thanks in advance. :)
> 
> Hmm, not sure I saw the previous versions. Guessing I wasn't on cc?

We switched to perf API from v4, and started ccing you and Mark from v5. :)

Thanks
Hao

> 
> Will

  reply	other threads:[~2019-11-25  8:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13  5:24 [PATCH v6 0/2] add performance reporting support to FPGA DFL drivers Wu Hao
2019-11-13  5:24 ` [PATCH v6 1/2] Documentation: fpga: dfl: add description for performance reporting support Wu Hao
2019-11-13  5:24 ` [PATCH v6 2/2] fpga: dfl: fme: add " Wu Hao
2019-11-27  1:45   ` Moritz Fischer
2019-11-25  3:34 ` [PATCH v6 0/2] add performance reporting support to FPGA DFL drivers Wu Hao
2019-11-25  8:01   ` Will Deacon
2019-11-25  8:08     ` Wu Hao [this message]
2019-12-09  2:45       ` Wu Hao
2019-12-16  1:01         ` Xu Yilum
2020-01-06  2:37           ` Wu Hao
2020-01-14  5:56             ` Wu Hao
2020-01-15  5:10               ` Moritz Fischer
2020-01-15  8:14                 ` Greg KH
2020-01-16  2:53                   ` Wu Hao

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=20191125080839.GA6227@hao-dev \
    --to=hao.wu@intel.com \
    --cc=atull@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mdf@kernel.org \
    --cc=will@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).