From: Andi Kleen <andi@firstfloor.org>
To: james northrup <northrup.james@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Andi Kleen <andi@firstfloor.org>, Roman Mamedov <rm@romanrm.ru>,
Johannes Stezenbach <js@sig21.net>,
"Markus F.X.J. Oberhumer" <markus@oberhumer.com>,
linux-kernel@vger.kernel.org, chris.mason@fusionio.com,
linux-btrfs@vger.kernel.org, Nitin Gupta <ngupta@vflare.org>,
Richard Purdie <rpurdie@openedhand.com>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Update LZO compression
Date: Fri, 17 Aug 2012 00:17:58 +0200 [thread overview]
Message-ID: <20120816221758.GM11413@one.firstfloor.org> (raw)
In-Reply-To: <CAPkEcwgv6f5B+Mrw7kzrHcZ5JZ+Yr0o=bLdoFqCB-e4CLiVx5A@mail.gmail.com>
On Thu, Aug 16, 2012 at 11:55:06AM -0700, james northrup wrote:
> looks like ARM results are inconclusive from a lot of folks without
> bandwidth to do a write-up, what about just plain STAGING status for ARM so
> the android tweakers can beat on it for a while?
Staging only really works for new drivers, not for updating existing
library functions like this.
I suppose you could keep both and have the architecture select with a
CONFIG.
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: andi@firstfloor.org (Andi Kleen)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Update LZO compression
Date: Fri, 17 Aug 2012 00:17:58 +0200 [thread overview]
Message-ID: <20120816221758.GM11413@one.firstfloor.org> (raw)
In-Reply-To: <CAPkEcwgv6f5B+Mrw7kzrHcZ5JZ+Yr0o=bLdoFqCB-e4CLiVx5A@mail.gmail.com>
On Thu, Aug 16, 2012 at 11:55:06AM -0700, james northrup wrote:
> looks like ARM results are inconclusive from a lot of folks without
> bandwidth to do a write-up, what about just plain STAGING status for ARM so
> the android tweakers can beat on it for a while?
Staging only really works for new drivers, not for updating existing
library functions like this.
I suppose you could keep both and have the architecture select with a
CONFIG.
-Andi
next prev parent reply other threads:[~2012-08-16 22:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 23:44 [GIT PULL] Update LZO compression Markus F.X.J. Oberhumer
2012-08-14 3:15 ` Andi Kleen
2012-08-14 10:10 ` Markus F.X.J. Oberhumer
2012-08-14 12:39 ` Johannes Stezenbach
2012-08-14 12:39 ` Johannes Stezenbach
2012-08-15 12:02 ` Markus F.X.J. Oberhumer
2012-08-15 12:02 ` Markus F.X.J. Oberhumer
2012-08-15 14:45 ` Johannes Stezenbach
2012-08-15 14:45 ` Johannes Stezenbach
2012-08-16 6:27 ` Markus F.X.J. Oberhumer
2012-08-16 6:27 ` Markus F.X.J. Oberhumer
2012-08-16 15:06 ` Johannes Stezenbach
2012-08-16 15:06 ` Johannes Stezenbach
2012-08-16 17:25 ` Roman Mamedov
2012-08-16 17:25 ` Roman Mamedov
2012-08-16 17:52 ` Andi Kleen
2012-08-16 17:52 ` Andi Kleen
2012-08-16 18:18 ` Geert Uytterhoeven
2012-08-16 18:18 ` Geert Uytterhoeven
2012-08-16 18:55 ` james northrup
2012-08-16 22:17 ` Andi Kleen [this message]
2012-08-16 22:17 ` Andi Kleen
2012-08-17 1:23 ` Mitch Harder
2012-08-17 1:23 ` Mitch Harder
2012-09-07 21:31 ` Andi Kleen
2012-09-07 21:31 ` Andi Kleen
2012-08-16 18:57 ` james northrup
2012-08-16 15:21 ` Jeff Garzik
2012-08-16 15:21 ` Jeff Garzik
2012-08-16 16:20 ` Andi Kleen
2012-08-16 16:20 ` Andi Kleen
2012-08-16 16:48 ` Jeff Garzik
2012-08-16 16:48 ` Jeff Garzik
2012-08-16 17:22 ` Johannes Stezenbach
2012-08-16 17:22 ` Johannes Stezenbach
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=20120816221758.GM11413@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=chris.mason@fusionio.com \
--cc=geert@linux-m68k.org \
--cc=js@sig21.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@oberhumer.com \
--cc=ngupta@vflare.org \
--cc=northrup.james@gmail.com \
--cc=richard.weinberger@gmail.com \
--cc=rm@romanrm.ru \
--cc=rpurdie@openedhand.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.