From: John Johansen <john.johansen@canonical.com>
To: Anca Emanuel <anca.emanuel@gmail.com>
Cc: kernel-team@lists.ubuntu.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Patch not upstream: fix race between open and removal of framebuffers
Date: Fri, 06 May 2011 22:04:49 -0700 [thread overview]
Message-ID: <4DC4D2F1.7080301@canonical.com> (raw)
In-Reply-To: <BANLkTikcbGVemWrs+3ZeAvLFafM339CP9w@mail.gmail.com>
On 05/05/2011 09:54 AM, Anca Emanuel wrote:
> On Thu, Apr 7, 2011 at 5:00 PM, Tim Gardner <tim.gardner@canonical.com> wrote:
>> On 04/02/2011 09:37 AM, Anca Emanuel wrote:
<< snip >>
> I can use de PC, but when it wake up from S3, hangs.
> full dmesg at: http://pastebin.com/rhMJrF2x
> uname -a
> Linux ubuntu 2.6.39-rc6 #7 SMP Wed May 4 12:26:39 EEST 2011 x86_64
> x86_64 x86_64 GNU/Linux
>
> I read that Ubuntu have something like 150 patches NOT upstreamed. Why ?
> And other guys complaining about the hard work they do to maintain
> stable and mainline.
>
> If you not upstream your work, then what is the ideea ? Keep it only
> for Ubuntu users ?
>
No, it a diff of about 150 patches for natty from the base 2.6.38 kernel.
We upstream our patches. Sometimes some patches will slip through for a
while, but they will go up.
Of the 150 or so patches not "upstream" there are only a few that are
ubuntu specific. Some of the patches are backports from patches upstream
for 2.6.39, some are from linux-next or other development branches,
and some are from projects that aren't upstream for one reason or another
(eg. aufs).
Our delta is public, well documented and available to be examined any
time. Just pull our kernels from
git://kernel.ubuntu.com/ubuntu/ubuntu-oneiric.git
git://kernel.ubuntu.com/ubuntu/ubuntu-natty.git
..
prev parent reply other threads:[~2011-05-07 5:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTikAc66kTknEKCX4Mbg7_9CGw+qDfQ@mail.gmail.com>
[not found] ` <4D9DC39A.2080207@canonical.com>
2011-05-05 16:54 ` Patch not upstream: fix race between open and removal of framebuffers Anca Emanuel
2011-05-05 16:56 ` Jesse Barnes
2011-05-05 18:00 ` Tim Gardner
2011-05-07 5:04 ` John Johansen [this message]
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=4DC4D2F1.7080301@canonical.com \
--to=john.johansen@canonical.com \
--cc=anca.emanuel@gmail.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@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 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.