From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Souza, Jose" <jose.souza@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: Re: [Intel-xe] [PATCH v2] drm/xe: Add fake workaround to maintain backward compatible in MI_BATCH_BUFFER_START
Date: Tue, 31 Jan 2023 16:04:08 +0200 [thread overview]
Message-ID: <87fsbq3inb.fsf@intel.com> (raw)
In-Reply-To: <116ea3da679ea8a34379fb83e8edc6842ae73419.camel@intel.com>
On Tue, 31 Jan 2023, "Souza, Jose" <jose.souza@intel.com> wrote:
> On Tue, 2023-01-31 at 09:24 +0200, Jani Nikula wrote:
>> On Mon, 30 Jan 2023, José Roberto de Souza <jose.souza@intel.com> wrote:
>> > +static const struct xe_rtp_entry lrc_additional_programming[] = {
>> > + { XE_RTP_NAME("FakeWaDisableNestedBBMode"),
>>
>> Please add newline after {, and indent with tabs not spaces.
>
> All the xe_rtp_entry arrays have this style pattern, just following
> what is already in the file.
Yuck. :p
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-01-31 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 16:17 [Intel-xe] [PATCH v2] drm/xe: Add fake workaround to maintain backward compatible in MI_BATCH_BUFFER_START José Roberto de Souza
2023-01-30 16:31 ` Lucas De Marchi
2023-01-30 17:15 ` Matt Roper
2023-01-30 18:04 ` Souza, Jose
2023-01-30 19:27 ` Lucas De Marchi
2023-01-30 19:43 ` Souza, Jose
2023-02-01 21:20 ` Rodrigo Vivi
2023-02-02 14:02 ` Souza, Jose
2023-02-02 23:14 ` Matt Roper
2023-02-06 22:09 ` Rodrigo Vivi
2023-01-31 7:24 ` Jani Nikula
2023-01-31 13:50 ` Souza, Jose
2023-01-31 14:04 ` Jani Nikula [this message]
2023-01-31 15:31 ` Lucas De Marchi
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=87fsbq3inb.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=lucas.demarchi@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 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.