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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20080427.163106.181887129.davem@davemloft.net>
Date:	Sun, 27 Apr 2008 16:31:06 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mingo@...e.hu
Cc:	James.Bottomley@...senPartnership.com, tglx@...utronix.de,
	linux-kernel@...r.kernel.org, hpa@...or.com
Subject: Re: [patch] x86, voyager: fix ioremap_nocache()

From: Ingo Molnar <mingo@...e.hu>
Date: Mon, 28 Apr 2008 01:18:09 +0200

> But, we'd not mind at all posting 1000 x86.git patches to lkml (or 
> another list) every 3 months (or more frequently), if people request 
> that.

Keep defending yourself Ingo.

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.

And you add patches before they are properly reviewed.

Look at all of the postings people have made this merge window about
x86 merge fallout(s).  This is exactly the chief gripe of everyone,
that you merge patches with little or no review into your tree.

People paying attention can see what your goal is.  You've expressed
in the past that you think we're not merging patches in fast enough,
which is quite a laugh, and now that you can do x86 maintainence
you're going to ramp things up and show everyone "how it's done."

And at what a great expense this experiment is being performed.  Just
ask anyone who has tried to get any work done this past week 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/