From: Archit Taneja <architt@codeaurora.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH RFC 0/9] omapdrm/omapfb/omapdss split
Date: Fri, 11 Dec 2015 17:02:37 +0530 [thread overview]
Message-ID: <566AB455.6070301@codeaurora.org> (raw)
In-Reply-To: <566A81EC.1090209@ti.com>
On 12/11/2015 01:27 PM, Tomi Valkeinen wrote:
>
> On 11/12/15 08:14, Archit Taneja wrote:
>
>> Is it possible to make omapfb get some of the old files (apply.c,
>> overlay.c, manager.c, sysfs files etc)? It might be helpful to have git
>> associate these files with omapfb/omap_vout since they have been the
>> only users of it. After cleanups, these files would eventually be
>> removed in the omapdrm copy, and it would be hard to track their history
>> using the omapfb copy.
>
> Good point. Unfortunately I don't know how I could do that...
>
> I need to keep all the files for a copy of omapdss intact, otherwise
> that copy won't work. So I need all the files for omapfb's copy, but I
> can't remove (i.e. move) any from the remaining copy...
>
> However, in the commit where I create the omapfb copy, I can add the
> original path in the commit description.
That should be good enough I guess.
Archit
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, hosted by The Linux Foundation
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-12-11 11:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 14:25 [PATCH RFC 0/9] omapdrm/omapfb/omapdss split Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 1/9] omapfb: allow compilation only if DRM_OMAP is disabled Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 2/9] omapfb: copy omapdss & displays for omapfb Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 3/9] omapdss: remove CONFIG_OMAP2_DSS_VENC from omapdss.h Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 4/9] omapfb/dss: change CONFIG_OMAP* to CONFIG_FB_OMAP* Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 5/9] omapfb/displays: change CONFIG_DISPLAY_* to CONFIG_FB_OMAP2_* Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 6/9] omapfb: take omapfb's prive omapdss into use Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 7/9] omapfb: move vrfb into omapfb Tomi Valkeinen
2015-12-13 19:13 ` Laurent Pinchart
2015-12-14 7:14 ` Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 8/9] drm/omap: move omapdss & displays under omapdrm Tomi Valkeinen
2015-12-13 19:08 ` Laurent Pinchart
2015-12-14 7:12 ` Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 9/9] drm/omap: make omapdrm select OMAP2_DSS Tomi Valkeinen
2015-12-10 14:53 ` [PATCH RFC 0/9] omapdrm/omapfb/omapdss split Rob Clark
2015-12-10 14:58 ` Tomi Valkeinen
2015-12-10 17:00 ` Emil Velikov
2015-12-10 17:15 ` Tomi Valkeinen
2015-12-11 6:14 ` Archit Taneja
2015-12-11 7:57 ` Tomi Valkeinen
2015-12-11 11:32 ` Archit Taneja [this message]
2015-12-16 15:52 ` Tomi Valkeinen
2015-12-16 22:11 ` Rob Clark
2015-12-17 0:22 ` Dave Airlie
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=566AB455.6070301@codeaurora.org \
--to=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).