From: Simon Horman <horms@verge.net.au>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] fbdev/drm: sh_mobile: remove unused MERAM support
Date: Mon, 30 Apr 2018 07:20:45 +0000 [thread overview]
Message-ID: <20180430072045.pveq4t63amanu6tx@verge.net.au> (raw)
In-Reply-To: <1524828105-26585-1-git-send-email-b.zolnierkie@samsung.com>
On Fri, Apr 27, 2018 at 01:21:42PM +0200, Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> This patchset removes unused MERAM support (last user was removed
> 3 years ago) from shmobile fbdev & drm drivers and then removes
> MERAM driver itself.
>
> If it is okay to merge this patches I would like patch #1 to go
> through fbdev tree and patch #2 to go through drm tree. Once they
> are both upstream (v4.18) I will apply patch #3 to fbdev tree.
Nice to see this cleanup, thanks.
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
prev parent reply other threads:[~2018-04-30 7:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180427112213epcas2p3ed6890af75e679b537121f2655aa91d8@epcas2p3.samsung.com>
2018-04-27 11:21 ` [PATCH 0/3] fbdev/drm: sh_mobile: remove unused MERAM support Bartlomiej Zolnierkiewicz
2018-04-27 11:21 ` [PATCH 1/3] video: fbdev: sh_mobile_lcdcfb: " Bartlomiej Zolnierkiewicz
2018-05-04 7:44 ` Geert Uytterhoeven
2018-04-27 11:21 ` [PATCH 2/3] drm: shmobile: " Bartlomiej Zolnierkiewicz
2018-04-27 11:21 ` [PATCH 3/3] video: fbdev: remove unused sh_mobile_meram driver Bartlomiej Zolnierkiewicz
2018-05-04 7:49 ` Geert Uytterhoeven
2018-04-27 11:36 ` [PATCH 0/3] fbdev/drm: sh_mobile: remove unused MERAM support Laurent Pinchart
2018-04-27 12:09 ` Daniel Vetter
2018-05-14 13:46 ` Bartlomiej Zolnierkiewicz
2018-04-30 7:20 ` Simon Horman [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=20180430072045.pveq4t63amanu6tx@verge.net.au \
--to=horms@verge.net.au \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.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