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
Date: Thu, 29 Oct 2020 10:14:12 +0100 [thread overview]
Message-ID: <20201029091412.GA3749125@kroah.com> (raw)
In-Reply-To: <d8211fcd-ddb5-34e1-1f9e-aa5b94a03889@gmx.de>
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
next prev parent reply other threads:[~2020-10-29 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 18:09 [PATCH 5.9 000/757] 5.9.2-rc1 review Ronald Warsow
2020-10-29 9:14 ` Greg KH [this message]
2020-10-29 14:42 ` Ronald Warsow
2020-10-29 19:17 ` Greg KH
2020-10-30 12:17 ` Ronald Warsow
-- strict thread matches above, loose matches on Subject: below --
2020-10-27 13:44 Greg Kroah-Hartman
2020-10-27 17:41 ` Jeffrin Jose T
2020-10-27 20:29 ` Naresh Kamboju
[not found] ` <20201028171208.GG118534@roeck-us.net>
2020-10-28 19:56 ` Guenter Roeck
2020-10-29 9:13 ` Jon Hunter
2020-10-29 10:43 ` Greg Kroah-Hartman
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=20201029091412.GA3749125@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rwarsow@gmx.de \
--cc=stable@vger.kernel.org \
/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