Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Matt Roper" <matthew.d.roper@intel.com>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	"Chris Wilson" <chris@chris-wilson.co.uk>,
	"Nathan Chancellor" <nathan@kernel.org>,
	linux-mm@kvack.org, "Andrzej Hajda" <andrzej.hajda@intel.com>,
	dri-devel@lists.freedesktop.org,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"David Airlie" <airlied@gmail.com>,
	"Matthew Auld" <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [REGRESSION] [BISECTED] Panic in gen8_ggtt_insert_entries() with v6.5
Date: Tue, 19 Sep 2023 20:15:21 +0100	[thread overview]
Message-ID: <ZQnzSQzspy6kejo4@casper.infradead.org> (raw)
In-Reply-To: <2554845.iZASKD2KPV@natalenko.name>

On Tue, Sep 19, 2023 at 08:11:47PM +0200, Oleksandr Natalenko wrote:
> I can confirm this one fixes the issue for me on T460s laptop. Thank you!

Yay!

> Should you submit it, please add:
> 
> Fixes: 0b62af28f2 ("i915: convert shmem_sg_free_table() to use a folio_batch")

Thanks for collecting all these; you're making my life really easy.
One minor point is that the standard format for Fixes: is 12 characters,
not 10.  eg,

Documentation/process/5.Posting.rst:    Fixes: 1f2e3d4c5b6a ("The first line of the commit specified by the first 12 characters of its SHA-1 ID")

I have this in my .gitconfig:

[pretty]
        fixes = Fixes: %h (\"%s\")

and in .git/config,

[core]
        abbrev = 12

I'm working on the commit message now.

  reply	other threads:[~2023-09-19 19:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-02 16:14 [Intel-gfx] [REGRESSION] Panic in gen8_ggtt_insert_entries() with v6.5 Oleksandr Natalenko
2023-09-19  8:26 ` [Intel-gfx] [REGRESSION] [BISECTED] " Oleksandr Natalenko
2023-09-19 13:23   ` Oleksandr Natalenko
2023-09-19 14:03     ` Bagas Sanjaya
2023-09-19 14:14       ` Oleksandr Natalenko
2023-09-19 15:43   ` Matthew Wilcox
2023-09-19 16:02     ` Matthew Wilcox
2023-09-19 18:11     ` Oleksandr Natalenko
2023-09-19 19:15       ` Matthew Wilcox [this message]
2023-09-19 14:08 ` [Intel-gfx] [REGRESSION] " Bagas Sanjaya
2023-09-29 13:45   ` Linux regression tracking #update (Thorsten Leemhuis)
2023-09-19 16:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-09-19 16:23   ` Matthew Wilcox
2023-09-19 16:12 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-19 16:30 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=ZQnzSQzspy6kejo4@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrzej.hajda@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matthew.auld@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=nathan@kernel.org \
    --cc=oleksandr@natalenko.name \
    --cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox