From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Wajdeczko, Michal" <Michal.Wajdeczko@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v3] drm/xe/oa: Fix kernel doc warnings in xe_drm.h
Date: Tue, 25 Jun 2024 19:04:28 -0700 [thread overview]
Message-ID: <87ikxwh32r.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <Zns2OqKffC-6Ua1y@intel.com>
On Tue, 25 Jun 2024 14:27:22 -0700, Rodrigo Vivi wrote:
>
> > Thanks everyone, I went ahead and merged this so that it gets into 6.11.
>
> I'm sorry for getting to late on this. Next time, please ensure that the
> subject tag is drm/xe/uapi: for anything touching uapi headers.
> Could even be drm/xe/uapi/oa: if needed to specify oa, but the 'uapi'
> is more useful on the history.
Sorry, yes will add uapi to the subject tag in the future if the patch
touches xe_drm.h.
Thanks.
--
Ashutosh
prev parent reply other threads:[~2024-06-26 2:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 20:31 [PATCH v3] drm/xe/oa: Fix kernel doc warnings in xe_drm.h Ashutosh Dixit
2024-06-23 20:35 ` ✓ CI.Patch_applied: success for drm/xe/oa: Fix kernel doc warnings in xe_drm.h (rev3) Patchwork
2024-06-23 20:36 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-23 20:37 ` ✓ CI.KUnit: success " Patchwork
2024-06-23 20:49 ` ✓ CI.Build: " Patchwork
2024-06-23 20:51 ` ✓ CI.Hooks: " Patchwork
2024-06-23 20:52 ` ✓ CI.checksparse: " Patchwork
2024-06-23 21:16 ` ✓ CI.BAT: " Patchwork
2024-06-23 22:11 ` ✗ CI.FULL: failure " Patchwork
2024-06-24 12:30 ` [PATCH v3] drm/xe/oa: Fix kernel doc warnings in xe_drm.h Michal Wajdeczko
2024-06-24 20:04 ` Dixit, Ashutosh
2024-06-24 20:18 ` Souza, Jose
2024-06-24 20:16 ` Dixit, Ashutosh
2024-06-25 17:22 ` Dixit, Ashutosh
2024-06-25 21:27 ` Rodrigo Vivi
2024-06-26 2:04 ` Dixit, Ashutosh [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=87ikxwh32r.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=Michal.Wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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.