From: Rob Landley <rob@landley.net>
To: "Samuel Masham" <samuel.masham@gmail.com>
Cc: "Ralf Baechle" <ralf@linux-mips.org>,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: 2.6.24 panics initializing ne2k in mips.
Date: Sat, 23 Feb 2008 15:43:22 -0600 [thread overview]
Message-ID: <200802231543.22810.rob@landley.net> (raw)
In-Reply-To: <93564eb70802222356u261d452aq8a3ad6ccc146d8dc@mail.gmail.com>
On Saturday 23 February 2008 01:56:42 Samuel Masham wrote:
> On Sat, Feb 23, 2008 at 7:19 AM, Rob Landley <rob@landley.net> wrote:
> > The patches that fixed it for me were:
> >
> > http://kernel.org/hg/index.cgi/linux-2.6/rev/85295
> > http://kernel.org/hg/index.cgi/linux-2.6/rev/85296
> >
> > Which, as you can see, were already committed to the kernel repository
> > during the 2.6.25 merge window.
...
> This fixes the 2.6.24 kernel for qemu, I would like to see these
> patches put into the stable series.
>
> Is that OK for everyone? if they are in the 2.6.25 tree then we just
> send the commit ids to the stable team...
Sounds good to me:
24649c00ca334955ac7d8a79f5a7834fc7ea441d
46f4f8f665080900e865392f4b3593be463bf0d8
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
prev parent reply other threads:[~2008-02-23 21:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 8:17 2.6.24 panics initializing ne2k in mips Rob Landley
2008-01-29 5:51 ` Rob Landley
2008-01-29 11:16 ` Ralf Baechle
2008-01-29 11:20 ` [PATCH 1/2] IRQ_NOPROBE helper functions Ralf Baechle
2008-01-29 11:21 ` [PATCH 2/2] MIPS: Mark all but i8259 interrupts as no-probe Ralf Baechle
2008-01-31 7:56 ` [PATCH 1/2] IRQ_NOPROBE helper functions Rob Landley
2008-02-22 14:17 ` 2.6.24 panics initializing ne2k in mips Samuel Masham
2008-02-22 22:19 ` Rob Landley
2008-02-23 7:56 ` Samuel Masham
2008-02-23 21:43 ` Rob Landley [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=200802231543.22810.rob@landley.net \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=samuel.masham@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox