From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-hardening@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH][next] drm/i915/uapi: Replace fake flex-array with flexible-array member
Date: Fri, 31 Mar 2023 10:02:05 +0300 [thread overview]
Message-ID: <87ileh2yky.fsf@intel.com> (raw)
In-Reply-To: <ef8d083a-a82b-669c-0b0a-959e0f120a26@embeddedor.com>
On Thu, 30 Mar 2023, "Gustavo A. R. Silva" <gustavo@embeddedor.com> wrote:
> Friendly ping: who can take this, please? 😄
It's in drm-intel-gt-next.
commit 02abecdeebfcd3848b26b70778dd7f6eb0db65e1
Author: Gustavo A. R. Silva <gustavoars@kernel.org>
AuthorDate: Fri Mar 17 12:18:01 2023 -0600
Commit: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
CommitDate: Tue Mar 21 08:41:18 2023 +0000
drm/i915/uapi: Replace fake flex-array with flexible-array member
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] drm/i915/uapi: Replace fake flex-array with flexible-array member
Date: Fri, 31 Mar 2023 10:02:05 +0300 [thread overview]
Message-ID: <87ileh2yky.fsf@intel.com> (raw)
In-Reply-To: <ef8d083a-a82b-669c-0b0a-959e0f120a26@embeddedor.com>
On Thu, 30 Mar 2023, "Gustavo A. R. Silva" <gustavo@embeddedor.com> wrote:
> Friendly ping: who can take this, please? 😄
It's in drm-intel-gt-next.
commit 02abecdeebfcd3848b26b70778dd7f6eb0db65e1
Author: Gustavo A. R. Silva <gustavoars@kernel.org>
AuthorDate: Fri Mar 17 12:18:01 2023 -0600
Commit: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
CommitDate: Tue Mar 21 08:41:18 2023 +0000
drm/i915/uapi: Replace fake flex-array with flexible-array member
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] drm/i915/uapi: Replace fake flex-array with flexible-array member
Date: Fri, 31 Mar 2023 10:02:05 +0300 [thread overview]
Message-ID: <87ileh2yky.fsf@intel.com> (raw)
In-Reply-To: <ef8d083a-a82b-669c-0b0a-959e0f120a26@embeddedor.com>
On Thu, 30 Mar 2023, "Gustavo A. R. Silva" <gustavo@embeddedor.com> wrote:
> Friendly ping: who can take this, please? 😄
It's in drm-intel-gt-next.
commit 02abecdeebfcd3848b26b70778dd7f6eb0db65e1
Author: Gustavo A. R. Silva <gustavoars@kernel.org>
AuthorDate: Fri Mar 17 12:18:01 2023 -0600
Commit: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
CommitDate: Tue Mar 21 08:41:18 2023 +0000
drm/i915/uapi: Replace fake flex-array with flexible-array member
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-03-31 7:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 18:18 [Intel-gfx] [PATCH][next] drm/i915/uapi: Replace fake flex-array with flexible-array member Gustavo A. R. Silva
2023-03-17 18:18 ` Gustavo A. R. Silva
2023-03-17 18:18 ` Gustavo A. R. Silva
2023-03-17 18:43 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-03-17 18:43 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-03-17 18:43 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2023-03-17 18:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-03-17 21:48 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-03-20 17:36 ` [Intel-gfx] [PATCH][next] " Kees Cook
2023-03-20 17:36 ` Kees Cook
2023-03-20 17:36 ` Kees Cook
2023-03-21 8:43 ` [Intel-gfx] " Tvrtko Ursulin
2023-03-21 8:43 ` Tvrtko Ursulin
2023-03-21 8:43 ` Tvrtko Ursulin
2023-03-30 20:13 ` [Intel-gfx] " Gustavo A. R. Silva
2023-03-30 20:13 ` Gustavo A. R. Silva
2023-03-30 20:13 ` Gustavo A. R. Silva
2023-03-31 7:02 ` Jani Nikula [this message]
2023-03-31 7:02 ` Jani Nikula
2023-03-31 7:02 ` Jani Nikula
2023-04-06 16:27 ` [Intel-gfx] " Gustavo A. R. Silva
2023-04-06 16:27 ` Gustavo A. R. Silva
2023-04-06 16:27 ` Gustavo A. R. Silva
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=87ileh2yky.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.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.