linux-kernel - Re: libata & no PCI: dma_[un]map

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: <20070605145149.GB2572@flint.arm.linux.org.uk>
Date:	Tue, 5 Jun 2007 15:51:49 +0100
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Christoph Hellwig <hch@...radead.org>,
	David Miller <davem@...emloft.net>, mroos@...ux.ee,
	linux-kernel@...r.kernel.org
Subject: Re: libata & no PCI: dma_[un]map_single undefined

On Tue, Jun 05, 2007 at 10:35:23AM -0400, Jeff Garzik wrote:
> 
> BTW, please fix your mailer.  It emits Mail-Followup-To headers that
> hijack everyone on the thread into the To field, breaking the normal
> LKML To/CC standard replying mechanism that has been working for a
> decade.

Sorry, I will not.  My local policy (which I have the utmost right to
have) is that I do not wish to be CC'd on responses to replies to my
posts.  Additional useless CC's are a waste of my limited bandwidth
and resources.

It's a question of local policy required by local resource limitations.

So I give you a choice: you can either have the benefit of me reply and
put up with the follow up header, or I will arrange to never reply to
your messages ever again (which may involve me never reading one again).
Which would you prefer?

rmk - who has regular fights with the OOM killer taking out name and
mail servers.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
-
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/