Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@samsung.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH V2] MAINTAINERS: Update Framebuffer file patterns
Date: Tue, 01 Jul 2014 06:31:43 +0000	[thread overview]
Message-ID: <002501cf94f6$2016bb20$60443160$%han@samsung.com> (raw)
In-Reply-To: <000801cf94e0$d5856cb0$80904610$%han@samsung.com>

On Tuesday, July 01, 2014 3:22 PM, Jingoo Han wrote:
> 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.

OK, I will only "update file patterns", and send v3 patch, soon.
After the patch is merged, I will send another patch to add extra
changes. Thank you for your comment. :-)

Best regards,
Jingoo Han

> 
>  Tomi
> 



      parent reply	other threads:[~2014-07-01  6:31 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
2014-07-01  6:31 ` Jingoo Han [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='002501cf94f6$2016bb20$60443160$%han@samsung.com' \
    --to=jg1.han@samsung.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