From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "Vetter, Daniel" <daniel.vetter@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Arjan van de Ven <arjan@linux.intel.com>,
"Goel, Akash" <akash.goel@intel.com>
Subject: Re: [PATCH 2/7] drm/i915: Resolving the memory region conflict for Stolen area
Date: Thu, 06 Mar 2014 08:21:31 +0200 [thread overview]
Message-ID: <87ha7bvod0.fsf@intel.com> (raw)
In-Reply-To: <87bnxrqqkh.fsf@intel.com>
On Fri, 28 Feb 2014, Jani Nikula <jani.nikula@intel.com> wrote:
> I'm keeping Akash's patch in -fixes for now as I've already pushed it
> there. Frankly, I'm inclined to queuing that one for 3.14 and fixing
> this right for 3.15, as it's a broken BIOS we're talking about, but I
> could be convinced otherwise. Particularly with the r-b and t-b.
Just following up on this: Akash's patch is now on its way to 3.14.
Chris, please rebase your patch on -nightly so we can get it ready for
3.15.
Thanks,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-03-06 6:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 10:55 [PATCH 2/7] drm/i915: Resolving the memory region conflict for Stolen area akash.goel
[not found] ` <8BF5CF93467D8C498F250C96583BC09CC6AD09@BGSMSX103.gar.corp.intel.com>
2014-01-28 9:14 ` Daniel Vetter
2014-02-18 19:49 ` Jesse Barnes
2014-02-24 19:22 ` Jani Nikula
2014-02-27 16:43 ` Chris Wilson
2014-02-28 14:06 ` Jani Nikula
2014-03-06 6:21 ` Jani Nikula [this message]
2014-02-26 16:21 ` Jesse Barnes
2014-02-27 8:59 ` Jani Nikula
2014-02-27 9:01 ` Jani Nikula
2014-03-03 19:14 ` Jesse Barnes
2014-03-03 22:33 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2014-01-09 5:30 akash.goel
2014-01-09 7:29 ` 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=87ha7bvod0.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=akash.goel@intel.com \
--cc=arjan@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.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.