From: Lyude Paul <lyude@redhat.com>
To: nouveau@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Ben Skeggs <bskeggs@redhat.com>
Subject: [PATCH v2 0/5] drm/nouveau: Backlight fixes and cleanup
Date: Wed, 29 Aug 2018 17:36:45 -0400 [thread overview]
Message-ID: <20180829213651.20874-1-lyude@redhat.com> (raw)
Next version of https://patchwork.freedesktop.org/series/48596/ . Made
some important changes to the refactoring patch, but everything else is
the same.
Lyude Paul (5):
drm/nouveau: Check backlight IDs are >= 0, not > 0
drm/nouveau: Move backlight device into nouveau_connector
drm/nouveau: s/nouveau_backlight_exit/nouveau_backlight_fini/
drm/nouveau: Cleanup indenting in nouveau_backlight.c
drm/nouveau: Refactor nvXX_backlight_init()
drivers/gpu/drm/nouveau/nouveau_backlight.c | 218 ++++++++++----------
drivers/gpu/drm/nouveau/nouveau_connector.c | 20 ++
drivers/gpu/drm/nouveau/nouveau_connector.h | 33 +++
drivers/gpu/drm/nouveau/nouveau_display.c | 2 -
drivers/gpu/drm/nouveau/nouveau_display.h | 25 ---
drivers/gpu/drm/nouveau/nouveau_drv.h | 2 -
6 files changed, 159 insertions(+), 141 deletions(-)
--
2.17.1
next reply other threads:[~2018-08-29 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 21:36 Lyude Paul [this message]
2018-08-29 21:36 ` [PATCH v2 1/5] drm/nouveau: Check backlight IDs are >= 0, not > 0 Lyude Paul
2018-08-29 21:36 ` [PATCH v2 2/5] drm/nouveau: Move backlight device into nouveau_connector Lyude Paul
2018-08-29 21:36 ` [PATCH v2 3/5] drm/nouveau: s/nouveau_backlight_exit/nouveau_backlight_fini/ Lyude Paul
2018-08-29 21:36 ` [PATCH v2 4/5] drm/nouveau: Cleanup indenting in nouveau_backlight.c Lyude Paul
2018-08-29 21:36 ` [PATCH v2 5/5] drm/nouveau: Refactor nvXX_backlight_init() Lyude Paul
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=20180829213651.20874-1-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).