All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	David Airlie <airlied@linux.ie>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 0/3] Reorder drivers/video directory
Date: Thu, 27 Feb 2014 18:16:13 +0000	[thread overview]
Message-ID: <530F80ED.1040509@infradead.org> (raw)
In-Reply-To: <1393502086-9433-1-git-send-email-tomi.valkeinen@ti.com>

On 02/27/2014 03:54 AM, Tomi Valkeinen wrote:
> Hi,
> 
> This is a re-send of the series, with RFC removed from the subject, and a bunch
> of acks added.
> 
> I'm cc'ing more people, to make sure this doesn't come as a surprise, and to
> make sure this is not a bad idea, doomed to fail horribly.

What does this patch apply to?  I can't get it to apply cleanly to
-rc4 or Linus's current git tree.

I like what I see so far.

Thanks.

> So this series creates a new directory, drivers/video/fbdev/, to which all
> fbdev related files are moved. Also, a new directory, drivers/video/fbdev/core/
> is created, to which the core fbdev framework files are moved. This makes the
> drivers/video hierarchy much more clear.
> 
> Presuming no one has objections to this as such, I wonder what's the least
> painful way to merge this? Normally, like any other fbdev change? As a separate
> pull request, maybe at -rc2 time frame, based on -rc1? Something else?


-- 
~Randy

WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@infradead.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	David Airlie <airlied@linux.ie>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 0/3] Reorder drivers/video directory
Date: Thu, 27 Feb 2014 10:16:13 -0800	[thread overview]
Message-ID: <530F80ED.1040509@infradead.org> (raw)
In-Reply-To: <1393502086-9433-1-git-send-email-tomi.valkeinen@ti.com>

On 02/27/2014 03:54 AM, Tomi Valkeinen wrote:
> Hi,
> 
> This is a re-send of the series, with RFC removed from the subject, and a bunch
> of acks added.
> 
> I'm cc'ing more people, to make sure this doesn't come as a surprise, and to
> make sure this is not a bad idea, doomed to fail horribly.

What does this patch apply to?  I can't get it to apply cleanly to
-rc4 or Linus's current git tree.

I like what I see so far.

Thanks.

> So this series creates a new directory, drivers/video/fbdev/, to which all
> fbdev related files are moved. Also, a new directory, drivers/video/fbdev/core/
> is created, to which the core fbdev framework files are moved. This makes the
> drivers/video hierarchy much more clear.
> 
> Presuming no one has objections to this as such, I wonder what's the least
> painful way to merge this? Normally, like any other fbdev change? As a separate
> pull request, maybe at -rc2 time frame, based on -rc1? Something else?


-- 
~Randy

  parent reply	other threads:[~2014-02-27 18:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 11:54 [PATCH 0/3] Reorder drivers/video directory Tomi Valkeinen
2014-02-27 11:54 ` Tomi Valkeinen
2014-02-27 11:54 ` Tomi Valkeinen
2014-02-27 11:54 ` [PATCH 1/3] video: move fbdev to drivers/video/fbdev Tomi Valkeinen
2014-02-27 11:54   ` Tomi Valkeinen
2014-02-27 11:54 ` [PATCH 2/3] fbdev: move fbdev core files to separate directory Tomi Valkeinen
2014-02-27 11:54   ` Tomi Valkeinen
2014-02-27 11:54   ` Tomi Valkeinen
2014-02-27 11:54 ` [PATCH 3/3] video: Kconfig: move drm and fb into separate menus Tomi Valkeinen
2014-02-27 11:54   ` Tomi Valkeinen
2014-02-27 11:54   ` Tomi Valkeinen
2014-02-27 18:16 ` Randy Dunlap [this message]
2014-02-27 18:16   ` [PATCH 0/3] Reorder drivers/video directory Randy Dunlap
2014-02-28  7:07   ` Tomi Valkeinen
2014-02-28  7:07     ` Tomi Valkeinen
2014-02-28  7:07     ` Tomi Valkeinen
2014-02-28  8:03     ` Geert Uytterhoeven
2014-02-28  8:03       ` Geert Uytterhoeven
2014-02-28  8:03       ` Geert Uytterhoeven
2014-03-03  8:45 ` Tomi Valkeinen
2014-03-03  8:45   ` Tomi Valkeinen
2014-03-03  8:45   ` Tomi Valkeinen
2014-03-04 19:21   ` Randy Dunlap
2014-03-04 19:21     ` Randy Dunlap
2014-03-05  6:32     ` Tomi Valkeinen
2014-03-05  6:32       ` Tomi Valkeinen
2014-03-05  6:32       ` Tomi Valkeinen
2014-03-04  9:50 ` Daniel Vetter
2014-03-04  9:50   ` Daniel Vetter
2014-03-04  9:50   ` Daniel Vetter

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=530F80ED.1040509@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=tomi.valkeinen@ti.com \
    --cc=torvalds@linux-foundation.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 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.