From: Christopher Harvey <charvey@matrox.com>
To: dri-devel <dri-devel@lists.freedesktop.org>
Cc: Mathieu Larouche <mathieu.larouche@matrox.com>
Subject: Re: [PATCH] mgag200 code cleanup patches
Date: Mon, 29 Apr 2013 14:59:10 -0400 [thread overview]
Message-ID: <8761z5b1tt.fsf@matrox.com> (raw)
In-Reply-To: <cover.1367260670.git.charvey@matrox.com>
Christopher Harvey <charvey@matrox.com> writes:
> I submitted these a while ago, but I think they got lost in the
> mailing list. Just wanted to make sure they get a shot at the merge
> window.
>
> thanks,
>
> Christopher Harvey (3):
> drm/mgag200: Remove pointless call to drm_fb_get_bpp_depth
> drm/mgag200: Pass driver specific mga_device in driver functions
> drm/mgag200: Remove extra variable assigns
>
> drivers/gpu/drm/mgag200/mgag200_fb.c | 3 ---
> drivers/gpu/drm/mgag200/mgag200_main.c | 2 --
> drivers/gpu/drm/mgag200/mgag200_mode.c | 7 +++----
> 3 files changed, 3 insertions(+), 9 deletions(-)
the drm-next branch is what gets merged into merge windows, right?
http://cgit.freedesktop.org/~airlied/linux/
--
next prev parent reply other threads:[~2013-04-29 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 18:37 [PATCH] mgag200 code cleanup patches Christopher Harvey
2013-02-18 22:33 ` [PATCH] drm/mgag200: Remove pointless call to drm_fb_get_bpp_depth Christopher Harvey
2013-02-20 14:34 ` [PATCH] drm/mgag200: Pass driver specific mga_device in driver functions Christopher Harvey
2013-02-20 14:36 ` [PATCH] drm/mgag200: Remove extra variable assigns Christopher Harvey
2013-04-29 18:59 ` Christopher Harvey [this message]
2013-04-30 0:21 ` [PATCH] mgag200 code cleanup patches Dave Airlie
2013-04-29 21:32 ` Paul Menzel
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=8761z5b1tt.fsf@matrox.com \
--to=charvey@matrox.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=mathieu.larouche@matrox.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 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.