mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Linux 2.6.9.1-pre1 contents
Date: Fri, 29 Oct 2004 11:04:36 -0400	[thread overview]
Message-ID: <200410291107_MC3-1-8D7A-1644@compuserve.com> (raw)

On Fri, 29 Oct 2004 at 12:33:04 +0100 Alan Cox wrote:

>> ide_maxtor_probe.patch
>>         Another Maxtor IDE drive serial number oddity
>
> This is definitely wrong,

  It just went into mainline as rev 1.87 to ide-probe.c  :(

  Your "Integrated Technology Express" addition is missing but I'm
going to add it here.


> the others look fairly sane although there are
> a lot that are for such obscure cases they seem to add not reduce risk.

  I've been including one-liners even if they only fix rare cases or
aren't strictly bugfixes, but the larger ones are riskier:

    - backport of the rq-lock patch almost certainly created a profiling
      bug if the retry path is taken.

    - the timers-and-signals patch fixes three things; only one is urgent.

  And Hugh's VM accounting patches look very worthwhile (they just went into
mainline.)  I took one and might merge the other two - but they change
statm reporting.


  Getting them to merge and compile is the easy part...


--Chuck Ebbert  29-Oct-04  11:02:40

             reply	other threads:[~2004-10-29 15:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29 15:04 Chuck Ebbert [this message]
2004-10-29 14:43 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2004-10-29 13:27 Chuck Ebbert
2004-10-29  2:02 Chuck Ebbert
2004-10-29  7:46 ` Chris Wedgwood
2004-10-29 11:33 ` Alan Cox

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=200410291107_MC3-1-8D7A-1644@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®