From: Mikulas Patocka <mpatocka@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"David Hildenbrand" <david@redhat.com>,
amd-gfx@lists.freedesktop.org, linux-mm@kvack.org,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Jann Horn" <jannh@google.com>,
"Pedro Falcato" <pfalcato@suse.de>
Subject: Re: [PATCH v3 3/3] amdgpu: don't report an error if the process was killed
Date: Wed, 7 Jan 2026 21:29:23 +0100 (CET) [thread overview]
Message-ID: <06317034-2677-d2ca-b468-841a2076e84d@redhat.com> (raw)
In-Reply-To: <7ffacc33-9233-4fa1-a7d8-28fb3fbb8061@lucifer.local>
On Mon, 5 Jan 2026, Lorenzo Stoakes wrote:
> Gentle nudge to ask you to please thread these series emails properly in
> future.
>
> Use something like:
>
> git format-patch --cover-letter --thread ...
>
> Or b4 or etc.
>
> This is a nightmare to try to review without it.
>
> Thanks!
I don't use git for patch development. I use quilt. I find git quite
awkward when I need to move between multiple patches and update them
independently.
I'll try to send the next version of this patchset using the 'quilt mail'
command.
Mikulas
next prev parent reply other threads:[~2026-01-07 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 21:17 Mikulas Patocka
2026-01-05 9:06 ` Christian König
2026-01-05 11:41 ` Lorenzo Stoakes
2026-01-07 20:29 ` Mikulas Patocka [this message]
2026-01-07 22:05 ` David Hildenbrand (Red Hat)
2026-01-05 12:13 ` Lorenzo Stoakes
2026-01-05 18:20 ` Liam R. Howlett
2026-01-08 9:10 ` Christian König
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=06317034-2677-d2ca-b468-841a2076e84d@redhat.com \
--to=mpatocka@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pfalcato@suse.de \
--cc=vbabka@suse.cz \
/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