[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201125235720.GR5487@ziepe.ca>
Date: Wed, 25 Nov 2020 19:57:20 -0400
From: Jason Gunthorpe <jgg@...pe.ca>
To: Christoph Hellwig <hch@...radead.org>
Cc: Daniel Vetter <daniel.vetter@...ll.ch>,
DRI Development <dri-devel@...ts.freedesktop.org>,
Intel Graphics Development <intel-gfx@...ts.freedesktop.org>,
Linux MM <linux-mm@...ck.org>, linux-xfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Thomas Hellstrom <thellstrom@...are.com>,
Brian Paul <brianp@...are.com>,
Daniel Vetter <daniel.vetter@...el.com>,
Christian Koenig <christian.koenig@....com>,
Huang Rui <ray.huang@....com>
Subject: Re: [PATCH] drm/ttm: don't set page->mapping
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
Powered by blists - more mailing lists