From: Paul Bolle <pebolle@tiscali.nl>
To: Rob Clark <robdclark@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
rupran@einserver.de, stefan.hengelein@fau.de,
Valentin Rothberg <valentinrothberg@gmail.com>
Subject: Re: drm/msm/mdp5: undefined CONFIG_MSM_BUS_SCALING
Date: Thu, 09 Apr 2015 21:38:45 +0200 [thread overview]
Message-ID: <1428608325.13881.37.camel@x220> (raw)
In-Reply-To: <CAF6AEGtUVPAwxXxQ-XAFrMp=HpwVPkyVgCGQgHW6Q_6jKH8tdg@mail.gmail.com>
On Thu, 2015-04-09 at 14:54 -0400, Rob Clark wrote:
> We are talking about a driver which does build and run on
> upstream kernel, and which has a few small #ifdef blocks to simplify
> backporting to downstream kernels (which we still do need to use for
> some generations and some devices)
This has comes up before too. My thoughts are basically that since it's
just a few blocks of code (I think we're discussing less than 200 lines
of code split over nine files here) it's hard to see why it would be
such a burden to carry those blocks in a separate tree until everything
can be submitted in actual working condition.
Paul Bolle
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Paul Bolle <pebolle@tiscali.nl>
To: Rob Clark <robdclark@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Valentin Rothberg <valentinrothberg@gmail.com>,
Hai Li <hali@codeaurora.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
rupran@einserver.de, stefan.hengelein@fau.de
Subject: Re: drm/msm/mdp5: undefined CONFIG_MSM_BUS_SCALING
Date: Thu, 09 Apr 2015 21:38:45 +0200 [thread overview]
Message-ID: <1428608325.13881.37.camel@x220> (raw)
In-Reply-To: <CAF6AEGtUVPAwxXxQ-XAFrMp=HpwVPkyVgCGQgHW6Q_6jKH8tdg@mail.gmail.com>
On Thu, 2015-04-09 at 14:54 -0400, Rob Clark wrote:
> We are talking about a driver which does build and run on
> upstream kernel, and which has a few small #ifdef blocks to simplify
> backporting to downstream kernels (which we still do need to use for
> some generations and some devices)
This has comes up before too. My thoughts are basically that since it's
just a few blocks of code (I think we're discussing less than 200 lines
of code split over nine files here) it's hard to see why it would be
such a burden to carry those blocks in a separate tree until everything
can be submitted in actual working condition.
Paul Bolle
next prev parent reply other threads:[~2015-04-09 19:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 11:22 drm/msm/mdp5: undefined CONFIG_MSM_BUS_SCALING Valentin Rothberg
2015-04-09 13:49 ` Rob Clark
2015-04-09 13:49 ` Rob Clark
2015-04-09 14:20 ` Greg KH
2015-04-09 14:50 ` Rob Clark
2015-04-09 14:50 ` Rob Clark
2015-04-09 17:07 ` Greg KH
2015-04-09 18:02 ` Rob Clark
2015-04-09 18:02 ` Rob Clark
2015-04-09 18:12 ` Paul Bolle
2015-04-09 18:54 ` Rob Clark
2015-04-09 18:54 ` Rob Clark
2015-04-09 19:38 ` Paul Bolle [this message]
2015-04-09 19:38 ` Paul Bolle
2015-04-09 19:44 ` Valentin Rothberg
2015-04-09 20:20 ` Rob Clark
2015-04-09 20:20 ` Rob Clark
2015-04-10 6:04 ` Valentin Rothberg
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=1428608325.13881.37.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=rupran@einserver.de \
--cc=stefan.hengelein@fau.de \
--cc=valentinrothberg@gmail.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 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.