public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: [Development] Kernel 3.3
Date: Tue, 15 May 2012 16:34:21 +0200	[thread overview]
Message-ID: <1337092461.15371.253.camel@rice-oxley.tremer.info> (raw)

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

Hey,

I have been working on the update to Linux 3.3 in the last weeks.
Unfortunately, I am running out if time in most things I do. So my
request is, that some of you test the kernel that I already compiled.

Scratch build:
  https://pakfire.ipfire.org/build/a740cfc3-1996-442b-87d7-a3432a6561f7

I don't expect anything weird, but I have not been able to test if it
boots up at all.

Make sure you check that the initrd has been generated after the
installation, reboot and then run a couple of things. That's all.

The reason for this kind of hurry is, that the release of Linux 3.4 is
imminent (probably this week) and I don't like to get stuck on a too old
kernel.

Michael


             reply	other threads:[~2012-05-15 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 14:34 Michael Tremer [this message]
2012-05-16 20:03 ` Stefan Schantl
2012-05-17 15:40   ` Michael Tremer

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=1337092461.15371.253.camel@rice-oxley.tremer.info \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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