From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [CI v4 1/3] drm/i915/guc: Move notification code into virtual function
Date: Thu, 11 May 2017 12:39:52 +0300 [thread overview]
Message-ID: <1494495592.4542.17.camel@linux.intel.com> (raw)
In-Reply-To: <20170510125928.51612-1-michal.wajdeczko@intel.com>
On ke, 2017-05-10 at 12:59 +0000, Michal Wajdeczko wrote:
> Prepare for alternate GuC notification mechanism.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
<SNIP>
> @@ -233,6 +236,10 @@ static inline int intel_guc_send(struct intel_guc *guc, const u32 *action, u32 l
> {
> return guc->send(guc, action, len);
> }
A newline is needed here. I'll fix it while pushing.
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
> +static inline void intel_guc_notify(struct intel_guc *guc)
> +{
> + guc->notify(guc);
> +}
>
> /* intel_guc_loader.c */
> int intel_guc_select_fw(struct intel_guc *guc);
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-05-11 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 12:59 [CI v4 1/3] drm/i915/guc: Move notification code into virtual function Michal Wajdeczko
2017-05-10 12:59 ` [CI v4 2/3] drm/i915/guc: Make scratch register base and count flexible Michal Wajdeczko
2017-05-10 12:59 ` [CI v4 3/3] HAX Enable GuC loading & submission Michal Wajdeczko
2017-05-10 13:29 ` ✓ Fi.CI.BAT: success for series starting with [CI,v4,1/3] drm/i915/guc: Move notification code into virtual function Patchwork
2017-05-11 9:39 ` Joonas Lahtinen [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=1494495592.4542.17.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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