From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <benjamin.widawsky@linux.intel.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Intel GFX <intel-gfx@lists.freedesktop.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH 00/12] Broadwell 3.14 backports
Date: Sat, 22 Mar 2014 12:29:21 +0100 [thread overview]
Message-ID: <20140322112921.GE26519@phenom.ffwll.local> (raw)
In-Reply-To: <20140322001732.GC2473@linux.intel.com>
On Fri, Mar 21, 2014 at 05:17:34PM -0700, Ben Widawsky wrote:
> On Fri, Mar 21, 2014 at 05:06:06PM -0700, Ben Widawsky wrote:
> > On Fri, Mar 21, 2014 at 04:47:05PM -0700, Greg KH wrote:
> > > I have no idea what is going on here, what this original email was from
> > > / about, or what I am supposed to do here...
> > >
> > > The stable patch process is pretty well defined, and documented, is that
> > > lacking somehow, and if so, in what?
> > >
> > > greg k-h
> >
> > My apologies, I didn't understand what Daniel had originally wanted from
> > me, and I think the plan changed a bit in flight. I'm sorry you got
> > dragged into it. The stable process documentation is perfectly adequate.
> >
>
> And if it wasn't clear, like Daniel said, please ignore these 12 patches
> for now. Sorry again.
For clarification: BDW support was enabled for the first time in 3.14, but
in the -rc phase suddenly lots of workaround patches and little fixes
start to pile in. Since pretty much no one has the hardware already I
decided to withold all bdw fixes and queued them for -next. Once it all
stabilized we could then reevaluate whether bdw support in 3.14 makes
sense or not, i.e. whether to backport a pile of fixes or just disable it
again.
bdw seems to have calmed down now and it doesn't look too bad (it's a bit
more than these 12 patches here, but all fairly isolated), so I've asked
Ben to assemble the required patches, backport and test them and then
submit it all to stable (once drm-next has landed, ofc). Ben was a bit
overeager and submitted them to stable a bit too early ;-)
My apologies for the fuzz and my unclear communication.
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-03-22 11:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 18:48 [PATCH 00/12] Broadwell 3.14 backports Ben Widawsky
2014-03-21 18:48 ` [PATCH 01/12] drm/i915: Fix forcewake counts for gen8 Ben Widawsky
2014-03-21 18:48 ` [PATCH 02/12] drm/i915: Do forcewake reset on gen8 Ben Widawsky
2014-03-21 18:48 ` [PATCH 03/12] drm/i915: Disable semaphore wait event idle message on BDW Ben Widawsky
2014-03-21 18:48 ` [PATCH 04/12] drm/i915: Implement WaDisableSDEUnitClockGating:bdw Ben Widawsky
2014-03-21 18:48 ` [PATCH 05/12] drm/i915: We implement WaDisableAsyncFlipPerfMode:bdw Ben Widawsky
2014-03-21 18:48 ` [PATCH 06/12] drm/i915: Add a partial instruction shootdown workaround on Broadwell Ben Widawsky
2014-03-21 18:48 ` [PATCH 07/12] drm/i915: Add thread stall DOP clock gating " Ben Widawsky
2014-03-21 18:48 ` [PATCH 08/12] drm/i915/bdw: The TLB invalidation mechanism has been removed from INSTPM Ben Widawsky
2014-03-21 18:48 ` [PATCH 09/12] drm/i915: Don't clobber CHICKEN_PIPESL_1 on BDW Ben Widawsky
2014-03-21 18:48 ` [PATCH 10/12] drm/i915: don't flood the logs about bdw semaphores Ben Widawsky
2014-03-21 22:06 ` [PATCH 10/12] [v2] " Ben Widawsky
2014-03-21 18:48 ` [PATCH 11/12] drm/i915/bdw: Use scratch page table for GEN8 PPGTT Ben Widawsky
2014-03-21 18:48 ` [PATCH 12/12] drm/i915/bdw: Restore PPAT on thaw Ben Widawsky
2014-03-21 19:49 ` [PATCH 00/12] Broadwell 3.14 backports Daniel Vetter
2014-03-21 22:14 ` Ben Widawsky
2014-03-21 23:47 ` Greg KH
2014-03-22 0:06 ` Ben Widawsky
2014-03-22 0:17 ` Ben Widawsky
2014-03-22 11:29 ` Daniel Vetter [this message]
2014-03-22 0:51 ` Ben Widawsky
2014-03-22 11:34 ` Daniel Vetter
2014-03-24 23:14 ` Ausmus, James
2014-03-24 23:17 ` Ben Widawsky
2014-03-25 9:43 ` 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=20140322112921.GE26519@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=benjamin.widawsky@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox