linux-kernel - Re: [patch] x86, voyager: fix ioremap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080428.021745.17554887.davem@davemloft.net>
Date:	Mon, 28 Apr 2008 02:17:45 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	alan@...rguk.ukuu.org.uk
Cc:	mingo@...e.hu, James.Bottomley@...senPartnership.com,
	tglx@...utronix.de, linux-kernel@...r.kernel.org, hpa@...or.com
Subject: Re: [patch] x86, voyager: fix ioremap_nocache()

From: Alan Cox <alan@...rguk.ukuu.org.uk>
Date: Mon, 28 Apr 2008 10:01:54 +0100

> > You can post whatever patches you like a million times to lkml.
> > That's not the problem.
> > 
> > It's that the patches don't get reviewed, posting them more or to a
> > different place doesn't help that.
> 
> So review them. Your comments strike me as the pot calling the kettle
> black given the way the network people like to live on their own mailing
> list.

Oh contraire.  Because we networking folks use a seperate mailing list
with a lower signal to noise ratio than lkml, and as a result more
specialization, more patches get more review by more specialists.

It's the point I'm trying to make every time the "post everything to
lkml" argument gets fronted.

Telling me to review all of this crud just ignores the problem.  And
the implication is that it's OK for unreviewed patches to go into the
tree, and it's most certainly not.

You might want to know that linux-next mainly exists because of how
much of this has been going on over the past half year or so.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/