All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: "Nirmoy Das" <nirmoy.das@intel.com>,
	intel-xe@lists.freedesktop.org,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH] drm/xe: Remove unused xe_bo->props struct
Date: Mon, 11 Mar 2024 12:49:40 -0400	[thread overview]
Message-ID: <Ze82JHUo52CQp5Qc@intel.com> (raw)
In-Reply-To: <5h56xqyuxiyspqklvqt4zzo23hgaqbevi6wt2bqimw7hnlfdlu@yyi7wlzmctxo>

On Mon, Mar 11, 2024 at 11:43:54AM -0500, Lucas De Marchi wrote:
> On Mon, Mar 11, 2024 at 12:33:29PM -0400, Rodrigo Vivi wrote:
> > On Mon, Mar 11, 2024 at 04:11:59PM +0100, Nirmoy Das wrote:
> > > Property struct is not being used so remove it and related dead code.
> > > 
> > > Fixes: ddfa2d6a846a ("drm/xe/uapi: Kill VM_MADVISE IOCTL")
> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > > Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
> > > Cc: intel-xe@lists.freedesktop.org
> > > Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> > 
> > Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> 
> afaics this is only removing dead code since it was not possible to set
> those props. I'm wondering if we should really keep the Fixes since
> technically we don't need this in 6.8 or 6.9. Thoughts?

good point.
Fixes tag can be avoided here.
And perhaps just cheery-pick later to fixes if some future patch
conflict with this.

But also if we are in later states of -fixes flow we can drop
the patch itself when we are cherry-picking the fixes.

and if we are in earlier stages of the fixes there's no problem
on sending a clean up up.

Up to you there.

> 
> Lucas De Marchi

  reply	other threads:[~2024-03-11 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 15:11 [PATCH] drm/xe: Remove unused xe_bo->props struct Nirmoy Das
2024-03-11 15:52 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-11 15:53 ` ✓ CI.checkpatch: " Patchwork
2024-03-11 15:54 ` ✓ CI.KUnit: " Patchwork
2024-03-11 16:06 ` ✓ CI.Build: " Patchwork
2024-03-11 16:06 ` ✓ CI.Hooks: " Patchwork
2024-03-11 16:07 ` ✓ CI.checksparse: " Patchwork
2024-03-11 16:33 ` ✓ CI.BAT: " Patchwork
2024-03-11 16:33 ` [PATCH] " Rodrigo Vivi
2024-03-11 16:43   ` Lucas De Marchi
2024-03-11 16:49     ` Rodrigo Vivi [this message]
2024-03-14  4:24       ` 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=Ze82JHUo52CQp5Qc@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=nirmoy.das@intel.com \
    --cc=thomas.hellstrom@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.