All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>, Ingo Molnar <mingo@kernel.org>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
	Dave Airlie <airlied@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Tom Gundersen <teg@jklm.no>
Subject: Re: [PATCH 00/11] SimpleDRM & Sysfb
Date: Fri, 07 Mar 2014 13:52:35 +0000	[thread overview]
Message-ID: <5319CF23.6090103@ti.com> (raw)
In-Reply-To: <CANq1E4QXWYQE5DWOA7F39oHFd2ZnV5Ny4ykOw1=aJT+B_umy3Q@mail.gmail.com>

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

On 07/03/14 15:05, David Herrmann wrote:

> If you can take these two patches, that's fine. They're not strictly
> needed by the series and I'd be happy to see them upstream. The other
> sysfb patches should be merged together, so I don't think there's much
> gain in applying them through fbdev.

Ok, I've applied them to fbdev tree.

> The DRM tree is usually merged late, anyway, so I'll see whether we
> will merge simpledrm through drm-next or not. If not, it'll be 3.16
> then. If you can get the fbdev merge in early, that should be enough
> for us to figure it out and provide a conflict-resolution. Btw., do
> you want the generic sysfb-helper in drivers/video/ or
> driver/video/fbdev? It's not limited to fbdev, so I'd put it in
> drivers/video/.

With a quick glance, it doesn't seem to depend on fbdev in any way,
right? That makes me think drivers/video/.

 Tomi



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

WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>, Ingo Molnar <mingo@kernel.org>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
	Dave Airlie <airlied@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Tom Gundersen <teg@jklm.no>
Subject: Re: [PATCH 00/11] SimpleDRM & Sysfb
Date: Fri, 7 Mar 2014 15:52:35 +0200	[thread overview]
Message-ID: <5319CF23.6090103@ti.com> (raw)
In-Reply-To: <CANq1E4QXWYQE5DWOA7F39oHFd2ZnV5Ny4ykOw1=aJT+B_umy3Q@mail.gmail.com>

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

On 07/03/14 15:05, David Herrmann wrote:

> If you can take these two patches, that's fine. They're not strictly
> needed by the series and I'd be happy to see them upstream. The other
> sysfb patches should be merged together, so I don't think there's much
> gain in applying them through fbdev.

Ok, I've applied them to fbdev tree.

> The DRM tree is usually merged late, anyway, so I'll see whether we
> will merge simpledrm through drm-next or not. If not, it'll be 3.16
> then. If you can get the fbdev merge in early, that should be enough
> for us to figure it out and provide a conflict-resolution. Btw., do
> you want the generic sysfb-helper in drivers/video/ or
> driver/video/fbdev? It's not limited to fbdev, so I'd put it in
> drivers/video/.

With a quick glance, it doesn't seem to depend on fbdev in any way,
right? That makes me think drivers/video/.

 Tomi



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

  reply	other threads:[~2014-03-07 13:52 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 14:14 [PATCH 00/11] SimpleDRM & Sysfb David Herrmann
2014-01-23 14:14 ` David Herrmann
2014-01-23 14:14 ` David Herrmann
2014-01-23 14:14 ` [PATCH 01/11] x86: sysfb: fool-proof CONFIG_X86_SYSFB David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:14 ` [PATCH 02/11] x86: sysfb: remove sysfb when probing real hw David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 16:51   ` Ingo Molnar
2014-01-23 16:51     ` Ingo Molnar
2014-01-23 17:07     ` David Herrmann
2014-01-23 17:07       ` David Herrmann
2014-01-23 17:07       ` David Herrmann
2014-01-23 17:14       ` Ingo Molnar
2014-01-23 17:14         ` Ingo Molnar
2014-01-23 19:09         ` David Herrmann
2014-01-23 19:09           ` David Herrmann
2014-01-23 19:09           ` David Herrmann
2014-01-24 10:16           ` Ingo Molnar
2014-01-24 10:16             ` Ingo Molnar
2014-01-23 14:14 ` [PATCH 03/11] fbdev: efifb: add dev->remove() callback David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:14 ` [PATCH 04/11] fbdev: vesafb: " David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:14 ` [PATCH 05/11] x86: sysfb: store apertures in simplefb platform-data David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:14 ` [PATCH 06/11] video: sysfb: add generic firmware-fb interface David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:14 ` [PATCH 07/11] drm: mgag200: remove redundant fbdev removal David Herrmann
2014-01-23 14:14   ` David Herrmann
2014-01-23 14:15 ` [PATCH 08/11] drm/i915: remove sysfbs early David Herrmann
2014-01-23 14:15   ` David Herrmann
2014-01-23 14:15 ` [PATCH 09/11] drm: add SimpleDRM driver David Herrmann
2014-01-23 14:15   ` David Herrmann
2014-01-23 14:15 ` [PATCH 10/11] drm: simpledrm: add fbdev fallback support David Herrmann
2014-01-23 14:15   ` David Herrmann
2014-01-23 14:15   ` David Herrmann
2014-01-23 14:15 ` [PATCH 11/11] x86/sysfb: allow sysfb+simpledrm combination David Herrmann
2014-01-23 14:15   ` David Herrmann
2014-01-23 14:15   ` David Herrmann
2014-01-27 22:18 ` [PATCH 00/11] SimpleDRM & Sysfb David Herrmann
2014-01-27 22:18   ` David Herrmann
2014-01-27 22:18   ` David Herrmann
2014-02-21  9:56   ` Thierry Reding
2014-02-21  9:56     ` Thierry Reding
2014-02-21  9:56     ` Thierry Reding
2014-03-03 10:12 ` Tomi Valkeinen
2014-03-03 10:12   ` Tomi Valkeinen
2014-03-03 10:12   ` Tomi Valkeinen
2014-03-03 10:29   ` David Herrmann
2014-03-03 10:29     ` David Herrmann
2014-03-03 10:29     ` David Herrmann
2014-03-03 10:45     ` Tomi Valkeinen
2014-03-03 10:45       ` Tomi Valkeinen
2014-03-03 11:09       ` David Herrmann
2014-03-03 11:09         ` David Herrmann
2014-03-03 11:09         ` David Herrmann
2014-03-03 11:22         ` Tomi Valkeinen
2014-03-03 11:22           ` Tomi Valkeinen
2014-03-06 12:16           ` David Herrmann
2014-03-06 12:16             ` David Herrmann
2014-03-06 12:16             ` David Herrmann
2014-03-07 12:44             ` Tomi Valkeinen
2014-03-07 12:44               ` Tomi Valkeinen
2014-03-07 13:05               ` David Herrmann
2014-03-07 13:05                 ` David Herrmann
2014-03-07 13:05                 ` David Herrmann
2014-03-07 13:52                 ` Tomi Valkeinen [this message]
2014-03-07 13:52                   ` Tomi Valkeinen
2014-03-07 14:06                   ` David Herrmann
2014-03-07 14:06                     ` David Herrmann
2014-03-07 14:06                     ` David Herrmann

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=5319CF23.6090103@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dh.herrmann@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=teg@jklm.no \
    /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.