From: Petri Latvala <petri.latvala@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915: Handle the case where legacy mmap is not available
Date: Tue, 11 May 2021 13:41:40 +0300 [thread overview]
Message-ID: <YJpfZMmb2Vu+/F8B@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <d97a3684-a7e1-53f7-ad1c-c5a34826d8ba@linux.intel.com>
On Tue, May 11, 2021 at 12:07:06PM +0200, Maarten Lankhorst wrote:
> Op 11-05-2021 om 11:50 schreef Petri Latvala:
> > On Tue, May 11, 2021 at 11:00:00AM +0200, Maarten Lankhorst wrote:
> >> We will remove support for the legacy mmap ioctl, so handle that
> >> case without rewriting all tests.
> >>
> >> When the gem_mmap ioctl is not available, transparently fallback to mmap_offset.
> >>
> >> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> >> ---
> >> Test-with: 20210510132305.1440923-1-maarten.lankhorst@linux.intel.com
> >
> > Test-with needs to be:
> >
> > - in cover letter, not in patch
> > - in kernel's cover letter, not IGT's
> >
> >
> >
> Thanks for the explanation!
>
> Is a cover letter required even for a single patch?
Yeah, T-W parsing is only done on the cover letter.
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2021-05-11 10:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 9:00 [igt-dev] [PATCH i-g-t] i915: Handle the case where legacy mmap is not available Maarten Lankhorst
2021-05-11 9:40 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-05-11 9:50 ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2021-05-11 10:07 ` Maarten Lankhorst
2021-05-11 10:41 ` Petri Latvala [this message]
2021-05-11 10:48 ` [igt-dev] ✓ Fi.CI.IGT: success for " Patchwork
2021-05-11 16:19 ` [igt-dev] [PATCH i-g-t] " Dixit, Ashutosh
2021-05-26 9:36 ` Maarten Lankhorst
2021-05-18 15:08 ` [igt-dev] ✓ Fi.CI.BAT: success for i915: Handle the case where legacy mmap is not available (rev2) Patchwork
2021-05-19 3:52 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-18 13:45 ` [igt-dev] ✓ Fi.CI.BAT: success for i915: Handle the case where legacy mmap is not available (rev3) Patchwork
2021-06-18 15:02 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-24 1:30 ` [igt-dev] [PATCH i-g-t] i915: Handle the case where legacy mmap is not available Dixit, Ashutosh
2021-06-24 9:02 ` Maarten Lankhorst
2021-06-24 18:33 ` Dixit, Ashutosh
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=YJpfZMmb2Vu+/F8B@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=maarten.lankhorst@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.