All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: "Kris Karas (Bug reporting)" <bugs-a21@moonlit-rail.com>
Cc: linux-kernel@vger.kernel.org,
	Peter Robinson <pbrobinson@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Borislav Petkov <bp@suse.de>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 0/2] video: A couple of fixes for the vga16fb driver
Date: Wed, 12 Jan 2022 12:38:01 +0100	[thread overview]
Message-ID: <2155e11e-beec-f896-0ab5-d48bb860f335@redhat.com> (raw)
In-Reply-To: <65a13d92-93fc-25d2-0009-b7e60f3392c4@moonlit-rail.com>

Hello Kris,

On 1/12/22 03:19, Kris Karas (Bug reporting) wrote:
> Hi Javier, Geert, et al,
> 
> Javier Martinez Canillas wrote:
>> Changes in v2:
>> - Make the change only for x86 (Geert Uytterhoeven)
>> - Only check the suppported video mode for x86 (Geert Uytterhoeven).
> 
> I just updated Bug 215001 to reflect that I have tested this new, V2 
> patch against 4 systems, one more than last time - 2 BIOS/VGAC and 2 
> UEFI - and it works perfectly on all four.
> 
> Thanks, Javier, for the excellent work!
> I didn't test with non-X86, but the code appears to bypass the patch on 
> non-X86, so should work fine for Geert.
> 
> Kris
> 
> Tested-By: Kris Karas <bugs-a21@moonlit-rail.com>
>

Thanks a lot for testing again!

I've applied patch #1 to drm-misc-next and #2 to drm-misc-fixes.

Best regards,
-- 
Javier Martinez Canillas
Linux Engineering
Red Hat


WARNING: multiple messages have this Message-ID (diff)
From: Javier Martinez Canillas <javierm@redhat.com>
To: "Kris Karas (Bug reporting)" <bugs-a21@moonlit-rail.com>
Cc: linux-fbdev@vger.kernel.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Peter Robinson <pbrobinson@gmail.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH v2 0/2] video: A couple of fixes for the vga16fb driver
Date: Wed, 12 Jan 2022 12:38:01 +0100	[thread overview]
Message-ID: <2155e11e-beec-f896-0ab5-d48bb860f335@redhat.com> (raw)
In-Reply-To: <65a13d92-93fc-25d2-0009-b7e60f3392c4@moonlit-rail.com>

Hello Kris,

On 1/12/22 03:19, Kris Karas (Bug reporting) wrote:
> Hi Javier, Geert, et al,
> 
> Javier Martinez Canillas wrote:
>> Changes in v2:
>> - Make the change only for x86 (Geert Uytterhoeven)
>> - Only check the suppported video mode for x86 (Geert Uytterhoeven).
> 
> I just updated Bug 215001 to reflect that I have tested this new, V2 
> patch against 4 systems, one more than last time - 2 BIOS/VGAC and 2 
> UEFI - and it works perfectly on all four.
> 
> Thanks, Javier, for the excellent work!
> I didn't test with non-X86, but the code appears to bypass the patch on 
> non-X86, so should work fine for Geert.
> 
> Kris
> 
> Tested-By: Kris Karas <bugs-a21@moonlit-rail.com>
>

Thanks a lot for testing again!

I've applied patch #1 to drm-misc-next and #2 to drm-misc-fixes.

Best regards,
-- 
Javier Martinez Canillas
Linux Engineering
Red Hat


  parent reply	other threads:[~2022-01-12 11:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10  9:56 [PATCH v2 0/2] video: A couple of fixes for the vga16fb driver Javier Martinez Canillas
2022-01-10  9:56 ` Javier Martinez Canillas
2022-01-10  9:56 ` [PATCH v2 1/2] video: vga16fb: Fix logic that checks for the display standard Javier Martinez Canillas
2022-01-10  9:56   ` Javier Martinez Canillas
2022-01-10  9:56 ` [PATCH v2 2/2] video: vga16fb: Only probe for EGA and VGA 16 color graphic cards Javier Martinez Canillas
2022-01-10  9:56   ` Javier Martinez Canillas
2022-01-11 13:16 ` [PATCH v2 0/2] video: A couple of fixes for the vga16fb driver Maxime Ripard
2022-01-11 13:16   ` Maxime Ripard
2022-01-12  2:19 ` Kris Karas (Bug reporting)
2022-01-12  2:19   ` Kris Karas (Bug reporting)
2022-01-12  7:57   ` Geert Uytterhoeven
2022-01-12  7:57     ` Geert Uytterhoeven
2022-01-12 11:38   ` Javier Martinez Canillas [this message]
2022-01-12 11:38     ` Javier Martinez Canillas

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=2155e11e-beec-f896-0ab5-d48bb860f335@redhat.com \
    --to=javierm@redhat.com \
    --cc=bp@suse.de \
    --cc=bugs-a21@moonlit-rail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbrobinson@gmail.com \
    --cc=tzimmermann@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.