public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: "linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
	dim-tools@lists.freedesktop.org,
	Jingoo Han <jingoohan1@gmail.com>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	intel-gfx@lists.freedesktop.org,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Jiri Slaby <jslaby@suse.com>, Lee Jones <lee.jones@linaro.org>,
	Sean Paul <sean@poorly.run>
Subject: Re: [PULL] topic/remove-fbcon-notifiers for v5.3
Date: Tue, 18 Jun 2019 13:46:55 +0200	[thread overview]
Message-ID: <8b9f9f03-54a4-9bda-6d12-2c0a3d9610b4@linux.intel.com> (raw)
In-Reply-To: <7f6223e8-9945-fe43-5ed7-9a8df8c3bcd6@samsung.com>

Op 18-06-2019 om 13:17 schreef Bartlomiej Zolnierkiewicz:
> Hi,
>
> On 6/18/19 11:20 AM, Maarten Lankhorst wrote:
>> Op 14-06-2019 om 11:25 schreef Maarten Lankhorst:
>>> Hi all,
>>>
>>> As discussed with Daniel V, I'm just doing the paperwork here as drm-misc maintainer.
>>>
>>> This is the topic pull request for the fbdev notifier removal.
>>>
>>> Bar, please make a final check and pull into your fbdev tree.
>>>
>>> Lee, please make a final check and pull into your backlight tree.
>>>
>>> Greg, this is just fyi, you already acked all the vt and staging patches in here
>>> to land through other trees.
>>>
>>> I'll pull this into drm-misc-next once Bart & Lee acked it.
>>>
>>> Cheers, Maarten.
>> Bart, Lee, ping?
> Looks OK to me (I have test pulled it locally and there is only trivial
> merge conflict on removed mxsfb fbdev driver) but it seems that all
> patches miss your "S-o-B:" line (there is only "Reviewed-by:" tag which
> is OK but has a different meaning)?

Hey,

I created the topic branch, but daniel pushed the patches to it. :)

That explains why there's a R-B but no S-o-B.

Cheers,

Maarten

> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung R&D Institute Poland
> Samsung Electronics
>
>>> topic/remove-fbcon-notifiers-2019-06-14-1:
>>> ----------------------------------------------------------------
>>> topic/remove-fbcon-notifiers:
>>> - remove fbdev notifier usage for fbcon, as prep work to clean up the fbcon locking
>>> - assorted locking checks in vt/console code
>>> - assorted notifier and cleanups in fbdev and backlight code
>>>
>>> The following changes since commit d1fdb6d8f6a4109a4263176c84b899076a5f8008:
>>>
>>>   Linux 5.2-rc4 (2019-06-08 20:24:46 -0700)
>>>
>>> are available in the Git repository at:
>>>
>>>   git://anongit.freedesktop.org/drm/drm-misc tags/topic/remove-fbcon-notifiers-2019-06-14-1
>>>
>>> for you to fetch changes up to 1dcff4ae65185e8c0300972f6d8d39d9a9db2bda:
>>>
>>>   backlight: simplify lcd notifier (2019-06-13 10:07:20 +0200)
>>>
>>> ----------------------------------------------------------------
>>> Daniel Vetter (33):
>>>       dummycon: Sprinkle locking checks
>>>       fbdev: locking check for fb_set_suspend
>>>       vt: might_sleep() annotation for do_blank_screen
>>>       vt: More locking checks
>>>       fbdev/sa1100fb: Remove dead code
>>>       fbdev/cyber2000: Remove struct display
>>>       fbdev/aty128fb: Remove dead code
>>>       fbcon: s/struct display/struct fbcon_display/
>>>       fbcon: Remove fbcon_has_exited
>>>       fbcon: call fbcon_fb_(un)registered directly
>>>       fbdev/sh_mobile: remove sh_mobile_lcdc_display_notify
>>>       fbdev/omap: sysfs files can't disappear before the device is gone
>>>       fbdev: sysfs files can't disappear before the device is gone
>>>       staging/olpc: lock_fb_info can't fail
>>>       fbdev/atyfb: lock_fb_info can't fail
>>>       fbdev: lock_fb_info cannot fail
>>>       fbcon: call fbcon_fb_bind directly
>>>       fbdev: make unregister/unlink functions not fail
>>>       fbdev: unify unlink_framebuffer paths
>>>       fbdev/sh_mob: Remove fb notifier callback
>>>       fbdev: directly call fbcon_suspended/resumed
>>>       fbcon: Call fbcon_mode_deleted/new_modelist directly
>>>       fbdev: Call fbcon_get_requirement directly
>>>       Revert "backlight/fbcon: Add FB_EVENT_CONBLANK"
>>>       fbmem: pull fbcon_fb_blanked out of fb_blank
>>>       fbdev: remove FBINFO_MISC_USEREVENT around fb_blank
>>>       fb: Flatten control flow in fb_set_var
>>>       fbcon: replace FB_EVENT_MODE_CHANGE/_ALL with direct calls
>>>       vgaswitcheroo: call fbcon_remap_all directly
>>>       fbcon: Call con2fb_map functions directly
>>>       fbcon: Document what I learned about fbcon locking
>>>       staging/olpc_dcon: Add drm conversion to TODO
>>>       backlight: simplify lcd notifier
>>>
>>>  arch/arm/mach-pxa/am200epd.c                    |  13 +-
>>>  drivers/gpu/vga/vga_switcheroo.c                |  11 +-
>>>  drivers/media/pci/ivtv/ivtvfb.c                 |   6 +-
>>>  drivers/staging/fbtft/fbtft-core.c              |   4 +-
>>>  drivers/staging/olpc_dcon/TODO                  |   7 +
>>>  drivers/staging/olpc_dcon/olpc_dcon.c           |   6 +-
>>>  drivers/tty/vt/vt.c                             |  18 ++
>>>  drivers/video/backlight/backlight.c             |   2 +-
>>>  drivers/video/backlight/lcd.c                   |  12 -
>>>  drivers/video/console/dummycon.c                |   6 +
>>>  drivers/video/fbdev/aty/aty128fb.c              |  64 ----
>>>  drivers/video/fbdev/aty/atyfb_base.c            |   3 +-
>>>  drivers/video/fbdev/core/fbcmap.c               |   6 +-
>>>  drivers/video/fbdev/core/fbcon.c                | 313 ++++++++-----------
>>>  drivers/video/fbdev/core/fbcon.h                |   6 +-
>>>  drivers/video/fbdev/core/fbmem.c                | 399 +++++++++---------------
>>>  drivers/video/fbdev/core/fbsysfs.c              |  20 +-
>>>  drivers/video/fbdev/cyber2000fb.c               |   1 -
>>>  drivers/video/fbdev/neofb.c                     |   9 +-
>>>  drivers/video/fbdev/omap2/omapfb/omapfb-sysfs.c |  21 +-
>>>  drivers/video/fbdev/sa1100fb.c                  |  25 --
>>>  drivers/video/fbdev/savage/savagefb_driver.c    |   9 +-
>>>  drivers/video/fbdev/sh_mobile_lcdcfb.c          | 132 +-------
>>>  drivers/video/fbdev/sh_mobile_lcdcfb.h          |   5 -
>>>  include/linux/console_struct.h                  |   5 +-
>>>  include/linux/fb.h                              |  45 +--
>>>  include/linux/fbcon.h                           |  30 ++
>>>  27 files changed, 396 insertions(+), 782 deletions(-)


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-06-18 11:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  9:25 [PULL] topic/remove-fbcon-notifiers for v5.3 Maarten Lankhorst
2019-06-18  9:20 ` Maarten Lankhorst
2019-06-18 10:03   ` Lee Jones
2019-06-18 10:27     ` Daniel Vetter
2019-06-18 11:31       ` Lee Jones
2019-06-18 11:17   ` Bartlomiej Zolnierkiewicz
2019-06-18 11:46     ` Maarten Lankhorst [this message]
2019-06-19 13:42       ` Bartlomiej Zolnierkiewicz

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=8b9f9f03-54a4-9bda-6d12-2c0a3d9610b4@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=daniel.thompson@linaro.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jingoohan1@gmail.com \
    --cc=jslaby@suse.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=maxime.ripard@bootlin.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=sean@poorly.run \
    /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