Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 29 Oct 2020 10:14:12 +0100
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Ronald Warsow <rwarsow@gmx.de>
Cc:     linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 5.9 000/757] 5.9.2-rc1 review
Message-ID: <20201029091412.GA3749125@kroah.com>
References: <d8211fcd-ddb5-34e1-1f9e-aa5b94a03889@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <d8211fcd-ddb5-34e1-1f9e-aa5b94a03889@gmx.de>
Precedence: bulk

On Tue, Oct 27, 2020 at 07:09:52PM +0100, Ronald Warsow wrote:
> Hallo
> 
> this rc1 runs here (pure Intel-box) without errors.
> Thanks !
> 
> 
> An RPC (I'm thinking about since some month)
> ======
> 
> Wouldn't it be better (and not so much add. work) to sort the
> Pseudo-Shortlog towards subsystem/driver ?
> 
> something like this:
> 
> ...
> usb: gadget: f_ncm: allow using NCM in SuperSpeed Plus gadgets.
> usb: cdns3: gadget: free interrupt after gadget has deleted
> 
>    Lorenzo Colitti <lorenzo@google.com>
>    Peter Chen <peter.chen@nxp.com>
> ...
> 
> 
> Think of searching a bugfix in the shortlog.
> 
> With the current layout I need to read/"visual grep" the whole log.
> 
> With the new layout I'm able to jump to the "buggy" subsystem/driver and
> only need to read that part of the log to get the info if the bug is
> fixed or not yet

Do you have an example script that generates such a thing?  If so, I'll
be glad to look into it, but am not going to try to create it on my own,
sorry.

thanks,

greg k-h