From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "Manna, Animesh" <animesh.manna@intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v6] drm/i915/dsb: DSB code refactoring
Date: Tue, 14 Nov 2023 11:36:51 +0000 [thread overview]
Message-ID: <3cd04edb8c7546b0bc55ae2beadef60773232493.camel@intel.com> (raw)
In-Reply-To: <BL1PR11MB5979E2D7AE120E6788E51D6DF9B2A@BL1PR11MB5979.namprd11.prod.outlook.com>
On Tue, 2023-11-14 at 11:35 +0000, Manna, Animesh wrote:
>
> > -----Original Message-----
> > From: Coelho, Luciano <luciano.coelho@intel.com>
> > Sent: Tuesday, November 14, 2023 4:47 PM
> > To: Manna, Animesh <animesh.manna@intel.com>; intel-
> > gfx@lists.freedesktop.org
> > Cc: Nikula, Jani <jani.nikula@intel.com>
> > Subject: Re: [Intel-gfx] [PATCH v6] drm/i915/dsb: DSB code refactoring
> >
> > On Fri, 2023-11-10 at 08:55 +0530, Animesh Manna wrote:
> > > Refactor DSB implementation to be compatible with Xe driver.
> > >
> > > v1: RFC version.
> > > v2: Make intel_dsb structure opaque from external usage. [Jani]
> > > v3: Rebased on latest.
> > > v4:
> > > - Add boundary check in dsb_buffer_memset(). [Luca]
> > > - Use size_t instead of u32. [Luca]
> > > v5: WARN_ON() added for out of boudary case with some optimization.
> > [Luca]
> >
> > ...and what is different in v6?
>
> Rebased on latest and fix a rebase-miss which CI did not caught well. Before merging want the green signal from CI.
Okay, it's good to mention that.
Anyway, my r-b is still valid. ;)
--
Cheers,
Luca.
next prev parent reply other threads:[~2023-11-14 11:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 3:25 [Intel-gfx] [PATCH v6] drm/i915/dsb: DSB code refactoring Animesh Manna
2023-11-10 8:25 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dsb: DSB code refactoring (rev6) Patchwork
2023-11-10 8:26 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-11-10 8:44 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-14 11:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-14 11:17 ` [Intel-gfx] [PATCH v6] drm/i915/dsb: DSB code refactoring Coelho, Luciano
2023-11-14 11:35 ` Manna, Animesh
2023-11-14 11:36 ` Coelho, Luciano [this message]
2023-11-15 3:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dsb: DSB code refactoring (rev7) Patchwork
2023-11-15 3:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-11-15 3:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-15 8:00 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-15 8:01 ` Patchwork
2023-11-15 8:23 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dsb: DSB code refactoring (rev6) Patchwork
2023-11-16 21:57 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2023-11-16 22:02 ` Patchwork
2023-11-16 23:14 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dsb: DSB code refactoring (rev7) Patchwork
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=3cd04edb8c7546b0bc55ae2beadef60773232493.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=animesh.manna@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).