Date: Tue, 5 Jun 2007 17:48:30 -0400
From: Jeff Garzik <jeff@garzik.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: David Miller <davem@davemloft.net>, alan@lxorguk.ukuu.org.uk,
       hch@infradead.org, mroos@linux.ee, linux-kernel@vger.kernel.org
Subject: Re: libata & no PCI: dma_[un]map_single undefined
Message-ID: <20070605214830.GS31565@havoc.gtf.org>
References: <20070605151104.GG31565@havoc.gtf.org> <20070605151847.GD2572@flint.arm.linux.org.uk> <20070605152133.GE2572@flint.arm.linux.org.uk> <20070605.122745.118950378.davem@davemloft.net> <20070605212523.GB18027@flint.arm.linux.org.uk> <20070605213815.GA19648@flint.arm.linux.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070605213815.GA19648@flint.arm.linux.org.uk>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 931
Lines: 24

On Tue, Jun 05, 2007 at 10:38:15PM +0100, Russell King wrote:
> There is one final point on this which I wish to make, in case anyone
> has decided that this is caused by some recent change at my end.
> 
> I've been adding this header to all my messages for about the last seven
> years.  It's only *just* become a problem because someone here made a
> decision that it was a problem.

Search LKML for other mentions of Mail-Followup-To; this is far from the
first time it's been brought up.

I'm probably one of the few who actually investigated why their MUA was
suddenly doing weird, RFC-unfriendly things to the To/CC headers,
tracking it down the Mail-Followup-To header.

	Jeff


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