From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jeff Garzik <jeff@garzik.org>
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
Date: Tue, 5 Jun 2007 23:03:45 +0100 [thread overview]
Message-ID: <20070605220345.GA22705@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20070605214830.GS31565@havoc.gtf.org>
On Tue, Jun 05, 2007 at 05:48:30PM -0400, Jeff Garzik wrote:
> 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.
And rather than configuring your MUA to ignore the header...
You're using mutt, mutt can be configured so.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-06-05 22:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 20:23 libata & no PCI: dma_[un]map_single undefined Meelis Roos
2007-06-04 0:40 ` David Miller
2007-06-04 7:47 ` Christoph Hellwig
2007-06-04 17:19 ` Jeff Garzik
2007-06-05 11:22 ` Alan Cox
2007-06-05 13:56 ` Jeff Garzik
2007-06-05 14:17 ` Russell King
2007-06-05 14:25 ` Jeff Garzik
2007-06-05 14:35 ` Jeff Garzik
2007-06-05 14:51 ` Russell King
2007-06-05 14:56 ` Jeff Garzik
2007-06-05 14:59 ` Russell King
2007-06-05 15:11 ` Jeff Garzik
2007-06-05 15:18 ` Russell King
2007-06-05 15:21 ` Russell King
2007-06-05 19:27 ` David Miller
2007-06-05 21:25 ` Russell King
2007-06-05 21:38 ` Russell King
2007-06-05 21:48 ` Jeff Garzik
2007-06-05 22:03 ` Russell King [this message]
2007-06-05 22:16 ` Jeff Garzik
2007-06-06 0:25 ` Valdis.Kletnieks
2007-06-05 15:41 ` Jeff Garzik
2007-06-05 15:45 ` Russell King
2007-06-05 19:27 ` David Miller
2007-06-05 19:24 ` David Miller
2007-06-05 21:10 ` Chuck Ebbert
2007-06-05 19:23 ` David Miller
2007-06-05 21:20 ` Russell King
2007-06-05 15:50 ` Alan Cox
2007-06-05 15:52 ` Russell King
2007-06-04 7:54 ` Geert Uytterhoeven
2007-06-04 13:30 ` Alan Cox
2007-06-04 21:22 ` David Miller
2007-06-05 0:56 ` William Lee Irwin III
2007-06-05 11:12 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070605220345.GA22705@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.