All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Anson Jacob <Anson.Jacob@amd.com>
Cc: Harry.Wentland@amd.com, Sunpeng.Li@amd.com,
	qingqing.zhuo@amd.com, Rodrigo.Siqueira@amd.com,
	roman.li@amd.com, amd-gfx@lists.freedesktop.org,
	Bhawanpreet.Lakha@amd.com, Aurabindo.Pillai@amd.com,
	paulus@samba.org, linuxppc-dev@lists.ozlabs.org, bindu.r@amd.com
Subject: Re: [RFC 2/2] drm/amd/display: Use PPC FPU functions
Date: Tue, 20 Jul 2021 07:06:51 +0100	[thread overview]
Message-ID: <YPZn+wqulTHSR+h2@infradead.org> (raw)
In-Reply-To: <20210719195211.520428-3-Anson.Jacob@amd.com>

>  #define DC_FP_END() kernel_fpu_end()
>  #elif defined(CONFIG_PPC64)
>  #include <asm/switch_to.h>
> +#define DC_FP_START() kernel_fpu_begin()
> +#define DC_FP_END() kernel_fpu_end()
>  #endif

Please use the same header as x86 in your first patch and then kill
this ifdefered and the DC_FP_START/DC_FP_END definitions entirely.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Anson Jacob <Anson.Jacob@amd.com>
Cc: Harry.Wentland@amd.com, Sunpeng.Li@amd.com, mpe@ellerman.id.au,
	qingqing.zhuo@amd.com, Rodrigo.Siqueira@amd.com,
	roman.li@amd.com, amd-gfx@lists.freedesktop.org,
	Bhawanpreet.Lakha@amd.com, Aurabindo.Pillai@amd.com,
	paulus@samba.org, christophe.leroy@csgroup.eu,
	benh@kernel.crashing.org, linuxppc-dev@lists.ozlabs.org,
	bindu.r@amd.com
Subject: Re: [RFC 2/2] drm/amd/display: Use PPC FPU functions
Date: Tue, 20 Jul 2021 07:06:51 +0100	[thread overview]
Message-ID: <YPZn+wqulTHSR+h2@infradead.org> (raw)
In-Reply-To: <20210719195211.520428-3-Anson.Jacob@amd.com>

>  #define DC_FP_END() kernel_fpu_end()
>  #elif defined(CONFIG_PPC64)
>  #include <asm/switch_to.h>
> +#define DC_FP_START() kernel_fpu_begin()
> +#define DC_FP_END() kernel_fpu_end()
>  #endif

Please use the same header as x86 in your first patch and then kill
this ifdefered and the DC_FP_START/DC_FP_END definitions entirely.
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  reply	other threads:[~2021-07-20  6:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 19:52 [RFC 0/2] Add generic FPU api similar to x86 Anson Jacob
2021-07-19 19:52 ` Anson Jacob
2021-07-19 19:52 ` [RFC 1/2] ppc/fpu: " Anson Jacob
2021-07-19 19:52   ` Anson Jacob
2021-07-20  6:04   ` Christoph Hellwig
2021-07-20  6:04     ` Christoph Hellwig
2021-07-20 19:30   ` kernel test robot
2021-07-19 19:52 ` [RFC 2/2] drm/amd/display: Use PPC FPU functions Anson Jacob
2021-07-19 19:52   ` Anson Jacob
2021-07-20  6:06   ` Christoph Hellwig [this message]
2021-07-20  6:06     ` Christoph Hellwig
2021-07-20 23:00   ` kernel test robot
2021-07-20  6:17 ` [RFC 0/2] Add generic FPU api similar to x86 Christian König
2021-07-20  6:17   ` Christian König
2022-03-02 16:00 ` Christophe Leroy

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=YPZn+wqulTHSR+h2@infradead.org \
    --to=hch@infradead.org \
    --cc=Anson.Jacob@amd.com \
    --cc=Aurabindo.Pillai@amd.com \
    --cc=Bhawanpreet.Lakha@amd.com \
    --cc=Harry.Wentland@amd.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=Sunpeng.Li@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bindu.r@amd.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=qingqing.zhuo@amd.com \
    --cc=roman.li@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.