[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YQEvUay+1Rzp04SO@kroah.com>
Date: Wed, 28 Jul 2021 12:20:01 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Pavel Machek <pavel@...x.de>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Carsten Schmid <carsten_schmid@...tor.com>
Subject: Re: [PATCH 5.10 167/167] xhci: add xhci_get_virt_ep() helper
On Wed, Jul 28, 2021 at 12:10:40PM +0200, Pavel Machek wrote:
> Hi!
>
> > From: Mathias Nyman <mathias.nyman@...ux.intel.com>
> >
> > [commit b1adc42d440df3233255e313a45ab7e9b2b74096 upstream]
>
> This is yet another variation in upstream commit making. So far I was
> using these:
>
> ma = re.match(".*Upstream commit ([0-9a-f]*) .*", l)
> if ma:
> m.upstream = ma.group(1)
> ma = re.match("[Cc]ommit ([0-9a-f]*) upstream[.]*", l)
> if ma:
> m.upstream = ma.group(1)
> ma = re.match("[Cc]ommit: ([0-9a-f]*)", l)
> if ma:
> m.upstream = ma.group(1)
>
> I guess I could update second regexp to search anywhere in the
> line.... but at that point it will also match stuff like "commit 1234
> upstream is broken".
>
> Do you have suggestion how to extract upstream sha1 automatically?
I use:
grep -E -o '[0-9a-f]{40}'
Powered by blists - more mailing lists