From: Jani Nikula <jani.nikula@intel.com>
To: Samasth Norway Ananda <samasth.norway.ananda@oracle.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: samasth.norway.ananda@oracle.com, ville.syrjala@linux.intel.com,
rodrigo.vivi@intel.com
Subject: Re: [PATCH v2 0/2] drm/i915/gmbus: fix bugs
Date: Wed, 18 Mar 2026 12:19:00 +0200 [thread overview]
Message-ID: <61f99ea781c8e5d4d8a2588241fa3b91675e8f8a@intel.com> (raw)
In-Reply-To: <98b08a93d554455ea7db69f148d2928e1ee728c1@intel.com>
On Tue, 17 Mar 2026, Jani Nikula <jani.nikula@intel.com> wrote:
> On Mon, 16 Mar 2026, Samasth Norway Ananda <samasth.norway.ananda@oracle.com> wrote:
>> v1 -> v2
>> v1 just included both changes, the bug fix and typo change in same patch.
>> Separated them to two different patches for clarity.
>
> Thanks for the patches.
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
And pushed to drm-intel-next.
Thanks,
Jani.
>
>
>>
>> Samasth Norway Ananda (2):
>> drm/i915/gmbus: fix spurious timeout on 512-byte burst reads
>> drm/i915/gmbus: fix a typo in comment message
>>
>> drivers/gpu/drm/i915/display/intel_gmbus.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-03-18 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 23:19 [PATCH v2 0/2] drm/i915/gmbus: fix bugs Samasth Norway Ananda
2026-03-16 23:19 ` [PATCH v2 1/2] drm/i915/gmbus: fix spurious timeout on 512-byte burst reads Samasth Norway Ananda
2026-03-16 23:19 ` [PATCH v2 2/2] drm/i915/gmbus: fix a typo in comment message Samasth Norway Ananda
2026-03-17 8:50 ` [PATCH v2 0/2] drm/i915/gmbus: fix bugs Jani Nikula
2026-03-18 10:19 ` Jani Nikula [this message]
2026-03-17 10:11 ` ✓ i915.CI.BAT: success for " Patchwork
2026-03-18 0:51 ` ✓ i915.CI.Full: " 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=61f99ea781c8e5d4d8a2588241fa3b91675e8f8a@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=samasth.norway.ananda@oracle.com \
--cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox