From: Jason Gunthorpe <jgg@ziepe.ca>
To: Christoph Hellwig <hch@infradead.org>
Cc: Thomas Hellstrom <thellstrom@vmware.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
linux-xfs@vger.kernel.org, Linux MM <linux-mm@kvack.org>,
Huang Rui <ray.huang@amd.com>, Brian Paul <brianp@vmware.com>,
linux-fsdevel@vger.kernel.org,
Daniel Vetter <daniel.vetter@intel.com>,
Christian Koenig <christian.koenig@amd.com>
Subject: Re: [PATCH] drm/ttm: don't set page->mapping
Date: Wed, 25 Nov 2020 19:57:20 -0400 [thread overview]
Message-ID: <20201125235720.GR5487@ziepe.ca> (raw)
In-Reply-To: <20201125181129.GA1858@infradead.org>
On Wed, Nov 25, 2020 at 06:11:29PM +0000, Christoph Hellwig wrote:
> On Wed, Nov 25, 2020 at 02:06:06PM -0400, Jason Gunthorpe wrote:
> > It uses a empty 'cover-letter' commit and automatically transforms it
> > into exactly the right stuff. Keeps track of everything you send in
> > git, and there is a little tool to auto-run git range-diff to help
> > build change logs..
> >
> > https://github.com/jgunthorpe/Kernel-Maintainer-Tools/blob/master/gj_tools/cmd_send_patches.py
> >
> > I've been occasionaly wondering if I should suggest Konstantin add a
> > sending side to b4, maybe using some of those ideas..
> >
> > (careful if you run it, it does autosend without prompting)
>
> The looks pretty fancy. Here is my trivial patchbomb.sh script
>
> #!/bin/sh
>
> COVERLETTER=$1
> PATCHES=$2
>
> git send-email --annotate --to-cover --cc-cover $1 $2
>
> still needs the git basecommit..endcommit notation, but it fires
> up the series for review.
annotate is OK, I used that for a long time..
My main gripe was it didn't setup the to/cc until after the annotate
editor closes.
Jason
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-11-26 8:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 16:25 [PATCH v4 0/3] mmu_notifier vs fs_reclaim lockdep annotations Daniel Vetter
2020-11-25 16:25 ` [PATCH v4 1/3] mm: Track mmu notifiers in fs_reclaim_acquire/release Daniel Vetter
2020-11-25 16:25 ` [PATCH v4 2/3] mm: Extract might_alloc() debug check Daniel Vetter
2020-11-25 16:25 ` [PATCH v4 3/3] locking/selftests: Add testcases for fs_reclaim Daniel Vetter
2020-11-25 16:25 ` [PATCH] drm/ttm: don't set page->mapping Daniel Vetter
2020-11-25 16:28 ` Daniel Vetter
2020-11-25 18:06 ` Jason Gunthorpe
2020-11-25 18:16 ` Daniel Stone
[not found] ` <20201125181129.GA1858@infradead.org>
2020-11-25 23:57 ` Jason Gunthorpe [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-20 9:54 [PATCH 0/3] mmu_notifier fs fs_reclaim lockdep annotations Daniel Vetter
2020-11-20 9:54 ` [PATCH] drm/ttm: don't set page->mapping Daniel Vetter
2020-11-20 10:04 ` Christian König
2020-11-20 10:05 ` Daniel Vetter
2020-11-20 10:08 ` Christian König
2020-11-20 15:01 ` Daniel Vetter
2020-11-04 16:50 Daniel Vetter
2020-11-05 7:59 ` Christian König
2020-11-05 9:11 ` Daniel Vetter
2020-11-05 12:29 ` Christian König
2020-11-05 12:50 ` Daniel Vetter
2020-11-05 12:56 ` Christian König
2020-11-05 13:20 ` Daniel Vetter
2020-11-05 13:22 ` Christian König
2020-11-05 14:31 ` Daniel Vetter
2020-11-05 14:38 ` Daniel Vetter
2020-11-05 15:15 ` Christian König
2020-11-05 16:37 ` Daniel Vetter
2020-11-06 8:30 ` 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=20201125235720.GR5487@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=brianp@vmware.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@infradead.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ray.huang@amd.com \
--cc=thellstrom@vmware.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;
as well as URLs for NNTP newsgroup(s).