From: "David S. Miller" <davem@redhat.com>
To: Martin Diehl <lists@mdiehl.de>
Cc: lists@mdiehl.de, noah@caltech.edu,
irda-users@lists.sourceforge.net, netdev@oss.sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [irda-users] [PATCH] Make VLSI FIR depend on X86
Date: Tue, 21 Oct 2003 01:13:20 -0700 [thread overview]
Message-ID: <20031021011320.3fa6888f.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0310210929350.4246-100000@notebook.home.mdiehl.de>
On Tue, 21 Oct 2003 09:33:24 +0200 (CEST)
Martin Diehl <lists@mdiehl.de> wrote:
> One more question: Shouldn't the i386 implementation instead of being NOP
> just call flush_write_buffers() - at least this is what the vlsi-private
> implementation is doing at the moment?
That seems right, yes.
prev parent reply other threads:[~2003-10-21 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 6:41 [PATCH] Make VLSI FIR depend on X86 Noah J. Misch
2003-10-20 17:30 ` [irda-users] " Martin Diehl
2003-10-21 4:17 ` David S. Miller
2003-10-21 7:12 ` Martin Diehl
2003-10-21 7:12 ` David S. Miller
2003-10-21 7:33 ` Martin Diehl
2003-10-21 8:13 ` David S. Miller [this message]
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=20031021011320.3fa6888f.davem@redhat.com \
--to=davem@redhat.com \
--cc=irda-users@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@mdiehl.de \
--cc=netdev@oss.sgi.com \
--cc=noah@caltech.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).