From: Andrew Morton [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 04:12:59 -0800
On Tue, 13 Nov 2007 03:58:24 -0800 (PST) David Miller [EMAIL PROTECTED]
wrote:
From: Andrew Morton [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 03:49:16 -0800
Do you believe that our response to bug reports is
* Andrew Morton [EMAIL PROTECTED] wrote:
Do you believe that our response to bug reports is adequate?
Do you feel that making us feel and look like shit helps?
That doesn't answer my question.
See, first we need to work out whether we have a problem. If we do
this, then we can
Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich [EMAIL PROTECTED]
wrote:
..
with CONFIG_NO_HZ and/or CONFIG_HPET_TIMER set kernel 2.6.23 doesn't
boot (ARM, Timer)
http://bugzilla.kernel.org/show_bug.cgi?id=9229
Kernel: 2.6.23
No response from developers
..
Ingo Molnar wrote:
..
This is all QA-101 that _cannot be argued against on a rational basis_,
it's just that these sorts of things have been largely ignored for
years, in favor of the all-too-easy open source means many eyeballs and
that is our QA answer, which is a _good_ answer but by far
Mark Lord wrote:
Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich
[EMAIL PROTECTED] wrote:
..
..
Suspend to RAM resume hangs on a tickless (NO_HZ) kernel
http://bugzilla.kernel.org/show_bug.cgi?id=9275
Kernel: 2.6.23
This is HP notebook nc6320 T2400 945GM
No
On Nov 13, 2007 12:15 PM, Andrew Morton [EMAIL PROTECTED] wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich [EMAIL PROTECTED]
wrote:
This is the listing of the open bugs that are relatively new, around
2.6.22 and up. They are vaguely classified by specific area.
(not a full
Mark Lord wrote:
Ingo Molnar wrote:
..
This is all QA-101 that _cannot be argued against on a rational
basis_, it's just that these sorts of things have been largely ignored
for years, in favor of the all-too-easy open source means many
eyeballs and that is our QA answer, which is a _good_
On Tue, 2007-11-13 at 03:15 -0800, Andrew Morton wrote:
SCSI==
qla2xxx: driver initialization does not complete when booting with
Port connected
http://bugzilla.kernel.org/show_bug.cgi?id=9267
Kernel: 2.6.23.1
No
pata_pdc202xx_old excessive ATA bus errors
http://bugzilla.kernel.org/show_bug.cgi?id=9337
2.6.24-rc2
No response from developers
Untrue. We've been discussing it on list in the past and its now on
bugzilla. Not obvious from outside I realise. That one I'm afraid is
probably a longer
On Nov 13, 2007 3:08 PM, Mark Lord [EMAIL PROTECTED] wrote:
Ingo Molnar wrote:
..
This is all QA-101 that _cannot be argued against on a rational basis_,
it's just that these sorts of things have been largely ignored for
years, in favor of the all-too-easy open source means many eyeballs
On Nov 13, 2007 7:24 AM, Giacomo A. Catenazzi [EMAIL PROTECTED] wrote:
As a long time kernel tester, I see some problem with the
newer new development model. In the short merge windows,
after to much time, there are to many patches.
I think the root issue there is that it's hard to get all
On Tue, 13 Nov 2007, Mark Lord wrote:
Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich
[EMAIL PROTECTED] wrote:
..
with CONFIG_NO_HZ and/or CONFIG_HPET_TIMER set kernel 2.6.23 doesn't
boot (ARM, Timer)
http://bugzilla.kernel.org/show_bug.cgi?id=9229
On Tue, 13 Nov 2007, Mark Lord wrote:
Mark Lord wrote:
Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich
[EMAIL PROTECTED] wrote:
..
..
Suspend to RAM resume hangs on a tickless (NO_HZ) kernel
http://bugzilla.kernel.org/show_bug.cgi?id=9275
* Mark Lord [EMAIL PROTECTED] wrote:
Ingo Molnar wrote:
..
This is all QA-101 that _cannot be argued against on a rational basis_,
it's just that these sorts of things have been largely ignored for years,
in favor of the all-too-easy open source means many eyeballs and that is
our QA
* Benoit Boissinot [EMAIL PROTECTED] wrote:
For debugging, maybe it's time someone does an amazon ec2+s3 service
to automate the bisecting and create .deb/.rpm from git, I don't know
how much it would cost though.
a few months ago i estimated the costs of this and it's just a few
On Tue, 13 Nov 2007 14:40:29 +0100 Ingo Molnar wrote:
* Andrew Morton [EMAIL PROTECTED] wrote:
Do you believe that our response to bug reports is adequate?
Do you feel that making us feel and look like shit helps?
That doesn't answer my question.
See, first we need to
On Tue, Nov 13, 2007 at 07:57:54AM -0800, Ray Lee wrote:
On Nov 13, 2007 7:24 AM, Giacomo A. Catenazzi [EMAIL PROTECTED] wrote:
As a long time kernel tester, I see some problem with the
newer new development model. In the short merge windows,
after to much time, there are to many patches.
On Tue, Nov 13, 2007 at 04:52:32PM +0100, Benoit Boissinot wrote:
Btw, I used to test every -mm kernel. But since I've switched distros
(gentoo-ubuntu)
and I have less time, I feel it's harder to test -rc or -mm kernels (I
know this isn't a lkml problem
but more a distro problem, but I would
On Tue, 13 Nov 2007 09:33:21 -0600 James Bottomley wrote:
On Tue, 2007-11-13 at 03:15 -0800, Andrew Morton wrote:
SCSI==
qla2xxx: driver initialization does not complete when booting with
Port connected
The other an automated set of standard pre-built bisection points so
that testers can more easily localize a bug down to a few hundred
commits without needing to learn how to use git bisect (think Ubuntu
users).
Before that you want a flowchart or instruction list of boot options to
try. A
Theodore Tso wrote:
On Tue, Nov 13, 2007 at 04:52:32PM +0100, Benoit Boissinot wrote:
Btw, I used to test every -mm kernel. But since I've switched distros
(gentoo-ubuntu)
and I have less time, I feel it's harder to test -rc or -mm kernels (I
know this isn't a lkml problem
but more a distro
http://bugzilla.kernel.org/show_bug.cgi?id=9267
Kernel: 2.6.23.1
No response from developers
Urm, well, if no-one ever tells the SCSI list it's unrealistic to expect
anyone to be working on it. As far as I can tell, email was sent to
Andrew Vasquez only on 31 October. However, the
Thomas Gleixner wrote:
On Tue, 13 Nov 2007, Mark Lord wrote:
..
I *still* get very slow resume-from-RAM quite often here
(new in 2.6.23 kernel, wasn't there in early 2.6.23-rc*).
..
Something eventually times out after a minute or so
and it comes back. Cannot make it happen reliably,
unless
FILE SYSTEMS===
ext4: delalloc space accounting problem drops data
http://bugzilla.kernel.org/show_bug.cgi?id=9329
Kernel: 2.6.24-rc1
No response from developers
Actually, there has been a response (Eric asked in mailing list and
Ingo Molnar wrote:
for example git-bisect was godsent. I remember that years ago bisection
of a bug was a very laborous task so that it was only used as a final,
last-ditch approach for really nasty bugs. Today we can autonomouly
bisect build bugs via a simple shell command around git-bisect
Thomas Gleixner wrote:
On Tue, 13 Nov 2007, Mark Lord wrote:
Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich
[EMAIL PROTECTED] wrote:
..
with CONFIG_NO_HZ and/or CONFIG_HPET_TIMER set kernel 2.6.23 doesn't
boot (ARM, Timer)
On Tue, Nov 13, 2007 at 12:13:56PM -0500, Theodore Tso wrote:
On Tue, Nov 13, 2007 at 04:52:32PM +0100, Benoit Boissinot wrote:
Btw, I used to test every -mm kernel. But since I've switched distros
(gentoo-ubuntu)
and I have less time, I feel it's harder to test -rc or -mm kernels (I
know
On Tue, Nov 13, 2007 at 03:15:53AM -0800, Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich [EMAIL PROTECTED]
wrote:
PLATFORM===
xipImage is built so that uBoot cant run it (ARM)
On Tue, Nov 13, 2007 at 12:50:08PM -0500, Mark Lord wrote:
Ingo Molnar wrote:
for example git-bisect was godsent. I remember that years ago bisection of
a bug was a very laborous task so that it was only used as a final,
last-ditch approach for really nasty bugs. Today we can autonomouly
On Tue, Nov 13, 2007 at 05:07:21PM +0100, Thomas Gleixner wrote:
On Tue, 13 Nov 2007, Mark Lord wrote:
Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich
[EMAIL PROTECTED] wrote:
..
with CONFIG_NO_HZ and/or CONFIG_HPET_TIMER set kernel 2.6.23 doesn't
On Tue, 2007-11-13 at 12:50 -0500, Mark Lord wrote:
Ingo Molnar wrote:
for example git-bisect was godsent. I remember that years ago bisection
of a bug was a very laborous task so that it was only used as a final,
last-ditch approach for really nasty bugs. Today we can autonomouly
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 12:50:08PM -0500, Mark Lord wrote:
Ingo Molnar wrote:
for example git-bisect was godsent. I remember that years ago bisection of
a bug was a very laborous task so that it was only used as a final,
last-ditch approach for really nasty bugs. Today we
Given the wide range of ARM platforms today, it is utterly idiotic to
expect a single person to be able to provide responses for all ARM bugs.
I for one wish I'd never *VOLUNTEERED* to be a part of the kernel
bugzilla, and really *WISH* I could pull out of that function.
You can. Perhaps that
On Tue, Nov 13, 2007 at 01:18:43PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 12:50:08PM -0500, Mark Lord wrote:
Ingo Molnar wrote:
for example git-bisect was godsent. I remember that years ago bisection
of a bug was a very laborous task so that it was only used as a
On Tue, Nov 13, 2007 at 12:50:08PM -0500, Mark Lord wrote:
It's a 540MByte download over a slow link for everyone else.
Where do you get this number from?
$ du -sh .git/objects/pack/
249M.git/objects/pack/
$ du -sh .git/objects/
253M.git/objects/
ie about half what you claim.
--
Intel
Matthew Wilcox wrote:
On Tue, Nov 13, 2007 at 12:50:08PM -0500, Mark Lord wrote:
It's a 540MByte download over a slow link for everyone else.
Where do you get this number from?
$ du -sh .git/objects/pack/
249M.git/objects/pack/
$ du -sh .git/objects/
253M.git/objects/
ie about half
Adrian Bunk wrote:
...
I did bisecting myself, and I know that it costs time and work.
But the first point is the above one that it makes otherwise nearly
undebuggable problems debuggable and fixable.
..
Definitely useful, no question.
But the problem is now that kernel devs are addicted to
On Tue, 13 Nov 2007 09:46:08 -0800 Martin Bligh [EMAIL PROTECTED] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=9267
Kernel: 2.6.23.1
No response from developers
Urm, well, if no-one ever tells the SCSI list it's unrealistic to expect
anyone to be working on it. As far as
On Tue, Nov 13, 2007 at 01:43:53PM -0500, Mark Lord wrote:
Matthew Wilcox wrote:
ie about half what you claim.
..
No, it's from earlier in this very thread:
Adrian Bunk wrote:
git clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
..
mkdir t
cd t
git
Matthew Wilcox wrote:
On Tue, Nov 13, 2007 at 01:43:53PM -0500, Mark Lord wrote:
mkdir t
cd t
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
(wait half an hour)
/usr/bin/du -s linux-2.6
522732 linux-2.6
You're assuming that everything in linux-2.6 was
On Tue, Nov 13, 2007 at 11:33:44AM -0600, Larry Finger wrote:
I'm very encouraged to read of your expanded testing efforts. As a
bcm43xx developer, Ubuntu has been our problem distro, mostly
because your standard kernels have debugging turned off for bcm43xx.
When a Ubuntu user reports a
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 12:13:56PM -0500, Theodore Tso wrote:
On Tue, Nov 13, 2007 at 04:52:32PM +0100, Benoit Boissinot wrote:
Btw, I used to test every -mm kernel. But since I've switched distros
(gentoo-ubuntu)
and I have less time, I feel it's harder to test -rc or -mm
On Tue, 13 Nov 2007 04:32:07 -0800 (PST) David Miller [EMAIL PROTECTED] wrote:
From: Andrew Morton [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 04:12:59 -0800
On Tue, 13 Nov 2007 03:58:24 -0800 (PST) David Miller [EMAIL PROTECTED]
wrote:
From: Andrew Morton [EMAIL PROTECTED]
Date:
On Tue, Nov 13, 2007 at 01:47:10PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
...
I did bisecting myself, and I know that it costs time and work.
But the first point is the above one that it makes otherwise nearly
undebuggable problems debuggable and fixable.
..
Definitely useful, no
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 01:47:10PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
...
I did bisecting myself, and I know that it costs time and work.
But the first point is the above one that it makes otherwise nearly
undebuggable problems debuggable and fixable.
..
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 01:47:10PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
..
Another point is that it shifts the work from the few experienced
developers to the many users. Users (and voluntary testers) we have
many, but developer time for debugging bug reports is a
On Tue, Nov 13, 2007 at 02:12:57PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 01:47:10PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
...
I did bisecting myself, and I know that it costs time and work.
But the first point is the above one that it makes otherwise nearly
On Tue, Nov 13, 2007 at 04:32:07AM -0800, David Miller wrote:
Luckily if the report being ignored isn't chaff, it will show up again
(and again and again) and this triggers a reprioritization because not
only is the bug no longer chaff, it also now got a lot of information
tagged to it so it's
On Tue, Nov 13, 2007 at 09:08:32AM -0500, Mark Lord wrote:
Ingo Molnar wrote:
..
This is all QA-101 that _cannot be argued against on a rational basis_,
it's just that these sorts of things have been largely ignored for
years, in favor of the all-too-easy open source means many eyeballs
On Tue, Nov 13, 2007 at 08:30:35PM +0100, Adrian Bunk wrote:
There is this silly limit that noone can work more than 168 hours per
week on the Linux kernel, and some kernel developers seem to take the
liberty of spending even less time on kernel development...
That limit of 168 hours applies
On Tue, Nov 13, 2007 at 02:26:05PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 01:47:10PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
..
Another point is that it shifts the work from the few experienced
developers to the many users. Users (and voluntary testers) we
On Tue, 13 Nov 2007, Andrew Morton wrote:
I think that we're fairly good about working the regressions in
Adrian/Michal/Rafael's lists but once Linus releases 2.6.x we tend to let
the unsolved ones slide, and we don't pay as much attention to the
regressions which 2.6.x testers report.
Can't
On Tue, Nov 13, 2007 at 07:46:49PM +, Russell King wrote:
On Tue, Nov 13, 2007 at 08:30:35PM +0100, Adrian Bunk wrote:
There is this silly limit that noone can work more than 168 hours per
week on the Linux kernel, and some kernel developers seem to take the
liberty of spending even
Theodore Tso wrote:
Heh. I hadn't enabled CONFIG_BCM43XX_DEBUG myself, but I just changed
it for my next kernel build. This is a slightly different issue,
which is that sometimes _DEBUG options shouldn't be turned on by
default (because they really trash performance and bloat log size),
On Tue, Nov 13, 2007 at 07:32:19PM +, Russell King wrote:
...
There's another issue I want to raise concerning bugzilla. We have the
classic case of not enough people reading bugzilla bugs - which is one
of the biggest problems with bugzilla. Virtually no one in the ARM
community looks
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 02:26:05PM -0500, Mark Lord wrote:
..
If you've been making significant updates to a driver/subsystem,
and people are reporting that it is now broken for them,
What are significant updates?
Sometimes one person makes one small patch and this patch
Russell King wrote:
On Tue, Nov 13, 2007 at 09:08:32AM -0500, Mark Lord wrote:
Ingo Molnar wrote:
..
This is all QA-101 that _cannot be argued against on a rational basis_,
it's just that these sorts of things have been largely ignored for
years, in favor of the all-too-easy open source means
On Tue, 13 Nov 2007 19:32:19 + Russell King [EMAIL PROTECTED] wrote:
There's another issue I want to raise concerning bugzilla. We have the
classic case of not enough people reading bugzilla bugs - which is one
of the biggest problems with bugzilla. Virtually no one in the ARM
community
On Tue, 13 Nov 2007 21:00:30 +0100 (CET) Christian Kujau [EMAIL PROTECTED]
wrote:
On Tue, 13 Nov 2007, Andrew Morton wrote:
I think that we're fairly good about working the regressions in
Adrian/Michal/Rafael's lists but once Linus releases 2.6.x we tend to let
the unsolved ones slide,
Bug fixing is not about finding someone to blame, it's about getting the
bug fixed.
Partly - its also about understanding why the bug occurred and making it
not happen again.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
On Tue, Nov 13, 2007 at 03:13:46PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 02:26:05PM -0500, Mark Lord wrote:
..
If you've been making significant updates to a driver/subsystem,
and people are reporting that it is now broken for them,
What are significant updates?
I jump in this discussion hoping to have some more insight on git and to
report my experience as a tester. I consider myself as half-literate in
this (I am here since 1991, more or less, and I am able to compile a
kernel and even hand-apply a patch, although I am in no way a kernel
programmer).
On Tue, Nov 13, 2007 at 01:04:11PM -0800, Andrew Morton wrote:
...
Here's an important point: developers have a fixed amount of development
time. They spend some of that time fixing bugs and the rest of that time
on otherstuff. And while one could cook up all sorts of wonderful
process
On Tue, 13 November 2007 15:18:07 -0500, Mark Lord wrote:
I just find it weird that something can be known broken for several -rc*
kernels before I happen to install it, discover it's broken on my own
machine,
and then I track it down, fix it, and submit the patch, generally all
within a
On Tuesday, 13 of November 2007, Mark Lord wrote:
Matthew Wilcox wrote:
On Tue, Nov 13, 2007 at 01:43:53PM -0500, Mark Lord wrote:
mkdir t
cd t
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
(wait half an hour)
/usr/bin/du -s linux-2.6
522732
On Tue, 13 Nov 2007, Andrew Morton wrote:
There are a number of process things we _could_ do. Like
- have bugfix-only kernel releases
Adrian Bunk does (did?) this with 2.6.16.x, although it always seemed to
me like an unrewarded one man show. AFAIK not even the big distros are
begging for
On Tue, 13 Nov 2007 22:33:58 +0100 Jörn Engel [EMAIL PROTECTED] wrote:
On Tue, 13 November 2007 15:18:07 -0500, Mark Lord wrote:
I just find it weird that something can be known broken for several -rc*
kernels before I happen to install it, discover it's broken on my own
machine,
and
Romano Giannetti wrote:
This was what I did in my (in the end almost successful) bisecting when
trying to find the mmc problem (see the thread named 2.6.24-rc1 eat my
SD card). This is true in theory, but it has some problem. The this
commit does not compile is the easiest and in man
On Tue, Nov 13, 2007 at 12:52:22PM -0800, Andrew Morton wrote:
On Tue, 13 Nov 2007 19:32:19 + Russell King [EMAIL PROTECTED] wrote:
There's another issue I want to raise concerning bugzilla. We have the
classic case of not enough people reading bugzilla bugs - which is one
of the
Jörn Engel wrote:
On Tue, 13 November 2007 15:18:07 -0500, Mark Lord wrote:
I just find it weird that something can be known broken for several -rc*
kernels before I happen to install it, discover it's broken on my own machine,
and then I track it down, fix it, and submit the patch, generally
On Tue, 13 November 2007 13:56:58 -0800, Andrew Morton wrote:
It's relatively common that a regression in subsystem A will manifest as a
failure in subsystem B, and the report initially lands on the desk of the
subsystem B developers.
But that's OK. The subsystem B people are the ones
On Tue, 13 Nov 2007 22:18:01 + Russell King [EMAIL PROTECTED] wrote:
On Tue, Nov 13, 2007 at 12:52:22PM -0800, Andrew Morton wrote:
On Tue, 13 Nov 2007 19:32:19 + Russell King [EMAIL PROTECTED] wrote:
There's another issue I want to raise concerning bugzilla. We have the
classic
On Tue, Nov 13, 2007 at 06:25:16PM +, Alan Cox wrote:
Given the wide range of ARM platforms today, it is utterly idiotic to
expect a single person to be able to provide responses for all ARM bugs.
I for one wish I'd never *VOLUNTEERED* to be a part of the kernel
bugzilla, and really
On Tue, 13 Nov 2007 23:24:14 +0100 Jörn Engel [EMAIL PROTECTED] wrote:
On Tue, 13 November 2007 13:56:58 -0800, Andrew Morton wrote:
It's relatively common that a regression in subsystem A will manifest as a
failure in subsystem B, and the report initially lands on the desk of the
On Tue, 13 Nov 2007, Mark Lord wrote:
Thomas Gleixner wrote:
On Tue, 13 Nov 2007, Mark Lord wrote:
Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich
[EMAIL PROTECTED] wrote:
..
with CONFIG_NO_HZ and/or CONFIG_HPET_TIMER set kernel 2.6.23
On Tue, Nov 13, 2007 at 02:32:01PM -0800, Andrew Morton wrote:
On Tue, 13 Nov 2007 22:18:01 + Russell King [EMAIL PROTECTED] wrote:
On Tue, Nov 13, 2007 at 12:52:22PM -0800, Andrew Morton wrote:
On Tue, 13 Nov 2007 19:32:19 + Russell King [EMAIL PROTECTED] wrote:
There's another
On Tue, 13 Nov 2007 23:09:37 + Russell King [EMAIL PROTECTED] wrote:
On Tue, Nov 13, 2007 at 02:32:01PM -0800, Andrew Morton wrote:
On Tue, 13 Nov 2007 22:18:01 + Russell King [EMAIL PROTECTED] wrote:
On Tue, Nov 13, 2007 at 12:52:22PM -0800, Andrew Morton wrote:
On Tue, 13 Nov
On Tue, Nov 13, 2007 at 09:13:19PM +0100, Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 07:32:19PM +, Russell King wrote:
...
There's another issue I want to raise concerning bugzilla. We have the
classic case of not enough people reading bugzilla bugs - which is one
of the biggest
Thomas Gleixner wrote:
On Tue, 13 Nov 2007, Mark Lord wrote:
Thomas Gleixner wrote:
On Tue, 13 Nov 2007, Mark Lord wrote:
Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich
[EMAIL PROTECTED] wrote:
..
with CONFIG_NO_HZ and/or CONFIG_HPET_TIMER set kernel 2.6.23
On Tue, 13 Nov 2007 23:29:54 + Russell King [EMAIL PROTECTED] wrote:
On Tue, Nov 13, 2007 at 09:13:19PM +0100, Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 07:32:19PM +, Russell King wrote:
...
There's another issue I want to raise concerning bugzilla. We have the
classic case
On Tue, Nov 13, 2007 at 03:18:07PM -0500, Mark Lord wrote:
Russell King wrote:
On Tue, Nov 13, 2007 at 09:08:32AM -0500, Mark Lord wrote:
Ingo Molnar wrote:
..
This is all QA-101 that _cannot be argued against on a rational basis_,
it's just that these sorts of things have been largely
On Tuesday 13 November 2007 07:08, Mark Lord wrote:
Ingo Molnar wrote:
..
This is all QA-101 that _cannot be argued against on a rational basis_,
it's just that these sorts of things have been largely ignored for
years, in favor of the all-too-easy open source means many eyeballs and
On Tuesday 13 November 2007 10:56, Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 12:13:56PM -0500, Theodore Tso wrote:
On Tue, Nov 13, 2007 at 04:52:32PM +0100, Benoit Boissinot wrote:
Btw, I used to test every -mm kernel. But since I've switched distros
(gentoo-ubuntu)
and I have less
On Tuesday 13 November 2007 11:57, Gabriel C wrote:
The main problem is finding experienced developers who spend time on
looking into bug reports.
There are already. IMO the problem is the development model.
There are tons new features in each new kernel release and 'tons new bugs'
which
On 11/13/2007 04:12 PM, Alan Cox wrote:
Bug fixing is not about finding someone to blame, it's about getting the
bug fixed.
Partly - its also about understanding why the bug occurred and making it
not happen again.
Very few people think about that part.
-
To unsubscribe from this list:
From: Mark Lord [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 13:18:43 -0500
Mind you, no arguing that this is effective when that poor bloke has
a day free to download the git-tree and build/reboot a dozen times.
Like the internet, this time spent is beneficial because it's
pushing the work out to
On Tue, 13 Nov 2007 19:52:17 -0500
Chuck Ebbert [EMAIL PROTECTED] wrote:
On 11/13/2007 04:12 PM, Alan Cox wrote:
Bug fixing is not about finding someone to blame, it's about getting the
bug fixed.
Partly - its also about understanding why the bug occurred and making it
not happen
Please stop cross-posting this thread at least to linux-pcmcia
until your post is relevant to PCMCIA.
Sorry for being a bore. (Not that I don't love reading LKML
discussions, but I found that it took too much time, and now
they're over at linux-pcmcia too! :)
Thank you in advance.
//Peter
-
To
From: Andrew Morton [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 14:32:01 -0800
On Tue, 13 Nov 2007 22:18:01 + Russell King [EMAIL PROTECTED] wrote:
Find some other mailing list; I'm not hosting *nor* am I willing to run a
non-subscribers only mailing list. Period. Not negotiable, so
From: Russell King [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 23:40:33 +
ARM ep93xx defconfig has been broken since 2.6.23-git1 due to:
drivers/net/arm/ep93xx_eth.c:420: error: implicit declaration of function
'__netif_rx_schedule_prep'
caused by: [NET]: Make NAPI polling independent
On Tue, 13 Nov 2007 17:11:36 -0800 Stephen Hemminger [EMAIL PROTECTED] wrote:
On Tue, 13 Nov 2007 19:52:17 -0500
Chuck Ebbert [EMAIL PROTECTED] wrote:
On 11/13/2007 04:12 PM, Alan Cox wrote:
Bug fixing is not about finding someone to blame, it's about getting the
bug fixed.
On Tue, 13 Nov 2007 17:55:51 -0800 (PST) David Miller [EMAIL PROTECTED] wrote:
I've created [EMAIL PROTECTED]
Let me just say - I'm astonished at how little spam gets though the vger
lists. Considering how many times those email addresses must have been
added to spam databases.
It must be a
From: Andrew Morton [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 18:27:00 -0800
Let me just say - I'm astonished at how little spam gets though the vger
lists. Considering how many times those email addresses must have been
added to spam databases.
It must be a lot of work, and whoever is
rant on :) ... These aren't directed specifically at Andrew, but
everyone who merges patches or is involved in the release process.
On Wednesday 14 November 2007 08:04, Andrew Morton wrote:
On Tue, 13 Nov 2007 21:00:30 +0100 (CET) Christian Kujau
[EMAIL PROTECTED] wrote:
On Tue, 13 Nov 2007,
From: Martin Bligh [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 09:46:08 -0800
This is a technical issue with vger.kernel.org mailing lists that I've tried
addressing before - maybe davem can help fix it?
I think the problem is that certain mail headers show up multiple
times and this makes it
If so, MANITAINERS claims that it is subscribers-only. That would cause
some bug reporters to give up and go away.
Find some other mailing list; I'm not hosting *nor* am I willing to run a
non-subscribers only mailing list. Period. Not negotiable, so don't even
try to change my mind.
On Wed, Nov 14, 2007 at 06:56:06AM +0100, Sam Ravnborg wrote:
If so, MANITAINERS claims that it is subscribers-only. That would cause
some bug reporters to give up and go away.
Find some other mailing list; I'm not hosting *nor* am I willing to run a
non-subscribers only mailing
From: Sam Ravnborg [EMAIL PROTECTED]
Date: Wed, 14 Nov 2007 06:56:06 +0100
If so, MANITAINERS claims that it is subscribers-only. That would cause
some bug reporters to give up and go away.
Find some other mailing list; I'm not hosting *nor* am I willing to run a
non-subscribers
On Tue, Nov 13, 2007 at 05:39:45PM -0700, Denys Vlasenko wrote:
On Tuesday 13 November 2007 10:56, Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 12:13:56PM -0500, Theodore Tso wrote:
On Tue, Nov 13, 2007 at 04:52:32PM +0100, Benoit Boissinot wrote:
Btw, I used to test every -mm kernel. But
On Wednesday 14 November 2007 00:27, Adrian Bunk wrote:
You missed the following in my email:
we slowly scare them away due to the many bug reports without any
reaction.
The problem is that bug reports take time. If you go away from easy
things like compile errors then even things like
301 - 400 of 402 matches
Mail list logo
