From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Natalie Protasevich <protasnb@gmail.com>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Linux PM List <linux-pm@lists.linux-foundation.org>,
Linux SCSI List <linux-scsi@vger.kernel.org>
Subject: Re: 2.6.28-rc5: Reported regressions from 2.6.27
Date: Mon, 17 Nov 2008 20:36:46 +0900 [thread overview]
Message-ID: <1226921806.8582.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20081116182953.6231ae8c@lxorguk.ukuu.org.uk>
On Sun, 2008-11-16 at 18:29 +0000, Alan Cox wrote:
> > the majority of these patches have not been merged for over two weeks
> > (for almost three weeks in many cases and for over a _month_ in one case).
> > IMO, this is insane.]
>
> Some of them are quite serious too - some stuff is basically unusable in
> 2.6.28rc due to the vmalloc bug.
>
> Is there any reason why someone (Rafael ?) shouldn't simply submit all of
> those patches that look sensible, are reported to fix regressions and
> whose maintainer has not provided a reason to NOT apply them into the
> tree ?
There is for SCSI. Our two bugzilla entries each have several patches
(one has two, the other has four). The patches listed in the
regressions aren't necessarily going to be the ones applied (depending
on how the arguing and testing goes).
James
next prev parent reply other threads:[~2008-11-17 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 16:24 2.6.28-rc5: Reported regressions from 2.6.27 Rafael J. Wysocki
2008-11-16 18:29 ` Alan Cox
2008-11-17 11:36 ` James Bottomley [this message]
2008-11-16 18:43 ` Linus Torvalds
2008-11-16 19:28 ` Rafael J. Wysocki
2008-11-16 21:40 ` Maxim Levitsky
2008-11-17 21:39 ` Rafael J. Wysocki
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=1226921806.8582.6.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@kernel.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=protasnb@gmail.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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