From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Alexander Beregalov" <a.beregalov@gmail.com>
Cc: "Mariusz Kozlowski" <m.kozlowski@tuxland.pl>,
kernel-testers@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 4
Date: Sun, 7 Dec 2008 11:43:03 +1100 [thread overview]
Message-ID: <20081207114303.db19dc4b.sfr@canb.auug.org.au> (raw)
In-Reply-To: <a4423d670812060542u4c646891oc4db646b3f89b2ad@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
On Sat, 6 Dec 2008 16:42:40 +0300 "Alexander Beregalov" <a.beregalov@gmail.com> wrote:
>
> This patch should fix it.
> http://lkml.org/lkml/2008/12/4/249
And Alan already has that queued for linux-next.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-07 0:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 9:07 Stephen Rothwell
2008-12-04 14:00 ` next-2008-12-04: ca0106 compile fix Alexey Dobriyan
2008-12-04 14:28 ` Takashi Iwai
2008-12-04 14:04 ` next-2008-12-04: ubifs section fixlet Alexey Dobriyan
2008-12-04 14:18 ` Artem Bityutskiy
2008-12-05 0:50 ` linux-next: Tree for December 4 (netdev-related: several) Randy Dunlap
2008-12-05 7:06 ` next-2008-12-04: vm.bio_inline_vecs Alexey Dobriyan
2008-12-05 8:44 ` Jens Axboe
2008-12-06 12:04 ` linux-next: Tree for December 4 Mariusz Kozlowski
2008-12-06 13:42 ` Alexander Beregalov
2008-12-07 0:43 ` Stephen Rothwell [this message]
2008-12-09 7:07 ` next-20081104 - kernel panic on ia64 box, at __mutex_lock_interruptible_slowpath Kamalesh Babulal
2008-12-09 18:50 ` Luck, Tony
[not found] <200812061455.37331.m.kozlowski@tuxland.pl>
2008-12-06 17:01 ` linux-next: Tree for December 4 Stephen Hemminger
2008-12-06 17:30 ` Mariusz Kozlowski
2009-12-04 9:30 Stephen Rothwell
2009-12-04 9:44 ` Michal Simek
2009-12-04 10:44 ` Stephen Rothwell
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=20081207114303.db19dc4b.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=a.beregalov@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
/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
all inboxes | Powered by JetHome®