From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Zap some empty lines
Date: Mon, 25 Sep 2023 15:28:27 +0100 [thread overview]
Message-ID: <1ab10838-0517-3ad9-c92e-e452f5b97d30@linux.intel.com> (raw)
In-Reply-To: <ZRGVsijpw4hjzYNz@ashyti-mobl2.lan>
On 25/09/2023 15:14, Andi Shyti wrote:
> Hi Tvrtko,
>
> On Wed, Sep 20, 2023 at 09:57:15AM +0100, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Recent refactoring left an unsightly block of empty lines. Remove them.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Cc: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
>> Cc: Anusha Srivatsa <anusha.srivatsa@intel.com>
>> Cc: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
>
> as this isn't merged yet:
>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Thanks, I am catching up with things and this wasn't so important. If
you have a spare moment feel free to push it?
Regards,
Tvrtko
next prev parent reply other threads:[~2023-09-25 14:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 8:57 [Intel-gfx] [PATCH] drm/i915: Zap some empty lines Tvrtko Ursulin
2023-09-20 8:57 ` Tvrtko Ursulin
2023-09-20 9:08 ` [Intel-gfx] " Jani Nikula
2023-09-20 10:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-09-20 10:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-20 10:31 ` [Intel-gfx] [PATCH] " Sripada, Radhakrishna
2023-09-20 10:31 ` Sripada, Radhakrishna
2023-09-20 13:46 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2023-09-25 14:14 ` [Intel-gfx] [PATCH] " Andi Shyti
2023-09-25 14:28 ` Tvrtko Ursulin [this message]
2023-09-25 14:58 ` Andi Shyti
2023-09-25 14:58 ` Andi Shyti
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=1ab10838-0517-3ad9-c92e-e452f5b97d30@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=andi.shyti@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
/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.