All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Jeff Garzik <jeff@garzik.org>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
	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, 05 Jun 2007 20:25:15 -0400	[thread overview]
Message-ID: <20436.1181089515@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 05 Jun 2007 18:16:25 EDT." <20070605221625.GU31565@havoc.gtf.org>

[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]

On Tue, 05 Jun 2007 18:16:25 EDT, Jeff Garzik said:
> On Tue, Jun 05, 2007 at 11:03:45PM +0100, Russell King wrote:
> > And rather than configuring your MUA to ignore the header...
> 
> > You're using mutt, mutt can be configured so.
> 
> So, you are seriously proposing that EVERYONE reconfigure their MUA,
> because you are sending out bad headers?
> 
> Don't you think that is an unscalable solution, and an imposition?

Not only is it unscalable, it almost by definition is anti-social.  The only
times I've actually seen one in the wild, it's because some subscriber to a
mailing list wishes to subvert the list's culture in a manner worse than
a Reply-To: header.  I considered adding support for Mail-Followup-To: to
the exmh MUA, but decided against it, because it would basically mean that
every time I got one, I'd have to curse and moan and put the To: and cc: back
the way everybody *else* on the list wanted those to headers to behave. Kind
of hard to motivate myself to write Tk/Tcl code that will just mean a *worse*
user experience for myself...

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2007-06-06  0:26 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
2007-06-05 22:16                                     ` Jeff Garzik
2007-06-06  0:25                                       ` Valdis.Kletnieks [this message]
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=20436.1181089515@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --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 \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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.