From: Jani Nikula <jani.nikula@linux.intel.com>
To: Gerd Hoffmann <kraxel@redhat.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 3/3] drm/i915: switch to drm_fb_helper_remove_conflicting_pci_framebuffers
Date: Mon, 23 Sep 2019 11:18:49 +0300 [thread overview]
Message-ID: <87v9tjh1cm.fsf@intel.com> (raw)
In-Reply-To: <20190823090236.etu5xvekfu4jsuzp@sirius.home.kraxel.org>
On Fri, 23 Aug 2019, Gerd Hoffmann <kraxel@redhat.com> wrote:
> On Fri, Aug 23, 2019 at 10:30:35AM +0200, Daniel Vetter wrote:
>> On Fri, Aug 23, 2019 at 10:14 AM Gerd Hoffmann <kraxel@redhat.com> wrote:
>> >
>> > Whole series or just the i915 patch?
>>
>> Ok I just checked and this all landed in 5.1 already, I thought it was
>> more recent. I think that's good enough, push it all without more
>> waiting.
>
> Pushed to drm-misc-next.
After-the-fact nitpick: i915 maintainers were Cc'd on the original
patch, but not on the subsequent discussion on merging, or where to
merge. intel-gfx@ mailing list wasn't Cc'd at all, which means this
didn't get any pre-merge CI coverage we expect on every patch. I found
about this having been merged through a merge conflict.
If you don't see the ack from the maintainers, please ask.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-09-23 8:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 9:06 [PATCH 0/3] drm, fbdev: complete remove_conflicting_pci_framebuffers cleanup Gerd Hoffmann
2019-08-22 9:06 ` [PATCH 1/3] fbdev: drop res_id parameter from remove_conflicting_pci_framebuffers Gerd Hoffmann
2019-08-22 13:08 ` Daniel Vetter
2019-08-22 9:06 ` [PATCH 2/3] drm: drop resource_id parameter from drm_fb_helper_remove_conflicting_pci_framebuffers Gerd Hoffmann
2019-08-22 13:08 ` Daniel Vetter
2019-08-22 9:06 ` [PATCH 3/3] drm/i915: switch to drm_fb_helper_remove_conflicting_pci_framebuffers Gerd Hoffmann
2019-08-22 13:13 ` Daniel Vetter
2019-08-23 8:14 ` Gerd Hoffmann
2019-08-23 8:30 ` Daniel Vetter
2019-08-23 9:02 ` Gerd Hoffmann
2019-09-23 8:18 ` Jani Nikula [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=87v9tjh1cm.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=rodrigo.vivi@intel.com \
/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