Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH V2] MAINTAINERS: Update Framebuffer file patterns
Date: Tue, 01 Jul 2014 06:22:12 +0000	[thread overview]
Message-ID: <53B25394.8060906@ti.com> (raw)
In-Reply-To: <000801cf94e0$d5856cb0$80904610$%han@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

On 01/07/14 06:59, Jingoo Han wrote:
> Since the commit f7018c2 "video: move fbdev to drivers/video/fbdev",
> all framebuffer drivers were moved to fbdev directory. Thus, file
> patterns of these framebuffer drivers should be updated correctly.
> 
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
> Changes since v1:
> - Fix the typo from 'fbdevwmt_ge_rops.*' to 'fbdev/wmt_ge_rop/*', per Liu Ying
> 
>  MAINTAINERS |   76 ++++++++++++++++++++++++++++++-----------------------------
>  1 file changed, 39 insertions(+), 37 deletions(-)

Thanks! I was planning to do this but I seem to have forgotten about it...

<snip>

> @@ -3707,7 +3707,8 @@ FREESCALE DIU FRAMEBUFFER DRIVER
>  M:	Timur Tabi <timur@tabi.org>
>  L:	linux-fbdev@vger.kernel.org
>  S:	Maintained
> -F:	drivers/video/fsl-diu-fb.*
> +F:	drivers/video/fbdev/fsl-diu-fb.c
> +F:	include/linux/fsl-diu-fb.h

You have a few of extra changes like the above. I'd rather have the
"update file patterns" patch doing only that, and make the new changes
in a separate patch.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-07-01  6:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01  3:59 [PATCH V2] MAINTAINERS: Update Framebuffer file patterns Jingoo Han
2014-07-01  6:22 ` Tomi Valkeinen [this message]
2014-07-01  6:31 ` Jingoo Han

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=53B25394.8060906@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@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