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: <20080428094858.GF16379@cs181133002.pp.htv.fi>
Date:	Mon, 28 Apr 2008 12:48:58 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	David Miller <davem@...emloft.net>
Cc:	alan@...rguk.ukuu.org.uk, 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()

On Mon, Apr 28, 2008 at 02:17:45AM -0700, David Miller wrote:
> 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.
>...

I'd say the best solution is to do both.

Many people active only in some area want to read only stuff affecting 
their area and not linux-kernel that averaged at 525 emails per day in 
February.

But when I have time I skim over patches on linux-kernel, and when I see 
in the diffstat that a Makefile or Kconfig file gets touched I check 
whether I can spot any bugs there (and other people sometimes also spot
bugs in patches for areas they aren't active in).

And starting regression tracking was only possible since most bug 
reports went to linux-kernel, not only to a gazillion different lists.

That's why it might make sense to have everything on both specialized 
lists and linux-kernel.

If it is wanted to reduce the volume on linux-kernel, offloading the 
sending of patches to some new kernel-patches mailing list might be
an option. OTOH, patches and the discussion of patches seems to be
the signal on linux-kernel, not the noise..

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
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/