On Mon, 2020-03-02 at 11:49 +0200, Arkadiusz Hiler wrote: > On Fri, Feb 28, 2020 at 06:52:01PM +0000, Souza, Jose wrote: > > On Fri, 2020-02-28 at 12:21 +0200, Petri Latvala wrote: > > > On Thu, Feb 27, 2020 at 11:42:03PM +0000, Souza, Jose wrote: > > > > The following changes since commit > > > > efcfa03ae6100dfe523ebf612e03c3a90fc4c794: > > > > > > > > linux-firmware: Update firmware file for Intel Bluetooth > > > > AX201 > > > > (2020- > > > > 02-24 07:43:42 -0500) > > > > > > > > are available in the Git repository at: > > > > > > > > git://anongit.freedesktop.org/drm/drm-firmware tgl_dmc_2.06 > > > > > > > > for you to fetch changes up to > > > > e2396319167724e9ffddc377f300469923fccdcb: > > > > > > > > i915: Add DMC firmware v2.06 for TGL (2020-02-27 15:24:56 > > > > 2020 > > > > -0800) > > > > > > > > ------------------------------------------------------------- > > > > --- > > > > José Roberto de Souza (1): > > > > i915: Add DMC firmware v2.06 for TGL > > > > > > > > WHENCE | 3 +++ > > > > i915/tgl_dmc_ver2_06.bin | Bin 0 -> 18660 bytes > > > > 2 files changed, 3 insertions(+) > > > > create mode 100644 i915/tgl_dmc_ver2_06.bin > > > > > > Patchwork didn't pick up this PR, I suspect the extra newlines to > > > be > > > the issue. Can you try resending this without the automatic > > > newlines > > > before the commit shas? > > > > > > If patchwork recognizes it as a pull request, it will appear in > > > here: > > > https://patchwork.freedesktop.org/api/1.0/projects/intel-gfx/events/?page=1&since=2020-02-20&name=pull-request-new > > > > > > > Hi Petri > > > > Still needed? According to > > https://patchwork.freedesktop.org/patch/355624/?series=74048&rev=2 > > it > > was manually picked. > > Hey, > > Patchwork got defeated by the carriage return this time: > > 000000d0: 7369 746f 7279 2061 743a 0d0a 0d0a 2020 sitory at:.... > > Which doesn't match this regexp: > > git_re = re.compile(r'^The following changes since commit.*' + > r'^are available in the Git repository at:\n' > r'^\s*([\S]+://[^\n]+)$', > re.DOTALL | re.MULTILINE | re.IGNORECASE) > > I'll turn that \n into \s+ or $ but you may also want to double check > you mailing setup. Parsing mails is notoriously hard and error prone > - > those carriage returns may break something elsewhere for you. Thanks for the headsup Arek, will check that. > _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
