linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jordan Breeding <jordan.breeding@attbi.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.70-mm3
Date: Sat, 31 May 2003 17:02:33 -0500	[thread overview]
Message-ID: <3ED92679.2030208@attbi.com> (raw)
In-Reply-To: <20030531013716.07d90773.akpm@digeo.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

  I have some good new and some bad news about 2.5.70-mm3.

The good news:

  The reiserfs changes seem to be stable, I have been running this
kernel on an all reiserfs box since this morning and everything seems
completely fine with it.

The bad news:

  Somewhere in the changes brought in from Linus BK (I assume since
there were USB changes there, but none that I noticed in your changes),
all my USB keyboard LEDs stopped working.  Numlock and capslock still
seem to function correctly but the LEDs on the keyboard no longer work,
with 2.5.70-mm2 they worked on VTs and in X, with 2.5.70-mm3 they don't
work on either.

Jordan

Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.70/2.5.70-mm3/
> 
> . More ext3 fixes.  It seems fully recovered now.
> 
> . Some cleanups and enhancements to the O_SYNC rework.
> 
> . A couple of fairly significant reiserfs enhancements.  See the changelogs
>   in the individual patches for detail
> <snipped>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+2SZ9SigNyqq/SRwRAuNRAJ41zmOyRsBSAhfZgEnvtdEEvCM3lgCgnGuZ
awd9bdIuzRipIrQBM+sAvH8=
=rDoY
-----END PGP SIGNATURE-----

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2003-05-31 22:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-31  8:37 2.5.70-mm3 Andrew Morton
2003-05-31 14:09 ` 2.5.70-mm3: LVM/device-mapper seems broken Sean Neakums
     [not found]   ` <1054390711.13115.1.camel@chtephan.cs.pocnet.net>
     [not found]     ` <6uznl3jh25.fsf@zork.zork.net>
2003-05-31 15:11       ` Sean Neakums
2003-05-31 22:02 ` Jordan Breeding [this message]
2003-06-03 16:51 ` 2.5.70-mm3 Mingming Cao
2003-06-03 17:39   ` 2.5.70-mm3 Andrew Morton

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=3ED92679.2030208@attbi.com \
    --to=jordan.breeding@attbi.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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