public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Lucas <canolucas@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	stable <stable@vger.kernel.org>,
	"Kuoppala, Mika" <mika.kuoppala@intel.com>,
	Andreas Sturmlechner <andreas.sturmlechner@gmail.com>
Subject: Re: Linux 3.8.6
Date: Sat, 06 Apr 2013 19:56:30 -0300	[thread overview]
Message-ID: <5160A81E.2010505@gmail.com> (raw)
In-Reply-To: <CAKMK7uEF6sfvMvut7JVCjsKbgzarr8acqELnC0iLrHyKo=b+tQ@mail.gmail.com>

On 06/04/13 18:41, Daniel Vetter wrote:
> Maintainer reporting in. But can we please drag the context in again?
> -Daniel
>
> On Sat, Apr 6, 2013 at 8:44 PM, Lucas <canolucas@gmail.com> wrote:
>> Alright, CC'ing the mantainers as well.
>>
>> Thanks again,
>> Lucas
>>
>> On 06/04/13 15:18, Greg KH wrote:
>>>
>>>
>>> Sure, can you cc: the authors of those patches, and anyone who
>>> signed-off on them in order to get their approval as well?
>>>
>>> thanks,
>>>
>>> greg k-h
>>>
>>
>
>
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
>

Thanks for reporting in.

Somehow the thread got all messed up in LKML. It didn't parse correctly 
there, but it seems that Gmane did. Here is the link:

http://comments.gmane.org/gmane.linux.kernel.stable/48872

Good luck,
Lucas

  reply	other threads:[~2013-04-06 22:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 17:40 Linux 3.8.6 Greg KH
2013-04-05 17:40 ` Greg KH
2013-04-06 18:10 ` Lucas
2013-04-06 18:18   ` Greg KH
2013-04-06 18:44     ` Lucas
2013-04-06 21:41       ` Daniel Vetter
2013-04-06 22:56         ` Lucas [this message]
2013-04-07 18:28           ` Daniel Vetter
2013-04-08  1:17             ` Lucas

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=5160A81E.2010505@gmail.com \
    --to=canolucas@gmail.com \
    --cc=andreas.sturmlechner@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.kuoppala@intel.com \
    --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