From: Thomas Zimmermann <tzimmermann@suse.de>
To: David Airlie <airlied@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the drm-misc-fixes tree
Date: Fri, 10 Feb 2023 10:51:24 +0100 [thread overview]
Message-ID: <65b46616-0835-58b3-401f-7b0951301d4d@suse.de> (raw)
In-Reply-To: <CAMwc25r3EQG7hHkC7SU9omHWFGqto7RuUY9uVNkC6vXUF_hVtg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 984 bytes --]
Hi
Am 10.02.23 um 01:08 schrieb David Airlie:
> On Fri, Feb 10, 2023 at 9:47 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Hi all,
>>
>> The following commit is also in the drm-fixes tree as a different commit
>> (but the same patch):
>>
>> 94d8b6572a1f ("nvidiafb: detect the hardware support before removing console.")
>>
>> This is commit
>>
>> 04119ab1a49f ("nvidiafb: detect the hardware support before removing console.")
>>
>> in the drm-fixes tree.
>
> Just FYI misc team, I've force pushed drm-misc-fixes to drop this
> patch, please make sure any local misc fixes don't bring it back in if
> we can avoid it.
Sorry about that. I didn't realize that you already added the fix
directly to drm-fixes.
Best regards
Thomas
>
> Dave.
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-02-10 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 23:47 Stephen Rothwell
2023-02-10 0:08 ` David Airlie
2023-02-10 9:51 ` Thomas Zimmermann [this message]
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=65b46616-0835-58b3-401f-7b0951301d4d@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®