From: "David S. Miller" <davem@davemloft.net>
To: Fruhwirth Clemens <clemens@endorphin.org>
Cc: jmorris@redhat.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
michal@logix.cz
Subject: Re: [PATCH 01/04] Adding cipher mode context information to crypto_tfm
Date: Wed, 2 Feb 2005 15:34:49 -0800 [thread overview]
Message-ID: <20050202153449.1e92c29a.davem@davemloft.net> (raw)
In-Reply-To: <1107386909.19339.9.camel@ghanima>
On Thu, 03 Feb 2005 00:28:29 +0100
Fruhwirth Clemens <clemens@endorphin.org> wrote:
> I suspected unlikely to be a hint for the compiler to do better jump
> prediction and speculations. Remove?
I don't think it hurts, keep it in there.
When the final patch is made with James's requested fixups, I'll stick
this into the 2.6.12 pending tree.
Also, I think there will be objections to that studlyCaps naming you
said your other code has. Keep garbage like that in the x11 sources,
if you don't mind :-)
next prev parent reply other threads:[~2005-02-02 23:54 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 11:56 [PATCH 01/04] Adding cipher mode context information to crypto_tfm Fruhwirth Clemens
2005-01-24 12:31 ` James Morris
2005-01-24 22:31 ` Andrew Morton
2005-01-24 23:12 ` Fruhwirth Clemens
2005-01-25 15:52 ` James Morris
2005-01-25 17:38 ` Fruhwirth Clemens
2005-01-25 18:56 ` James Morris
2005-01-29 18:13 ` Fruhwirth Clemens
2005-01-29 18:23 ` Andrew Morton
2005-01-30 18:07 ` Fruhwirth Clemens
2005-02-02 22:46 ` James Morris
2005-02-02 23:28 ` Fruhwirth Clemens
2005-02-02 23:34 ` David S. Miller [this message]
2005-02-03 0:21 ` Fruhwirth Clemens
2005-02-03 0:29 ` David S. Miller
2005-02-03 0:40 ` Michal Ludvig
2005-02-03 8:55 ` Fruhwirth Clemens
2005-02-02 23:46 ` James Morris
2005-02-02 23:47 ` James Morris
2005-02-03 11:47 ` Fruhwirth Clemens
2005-02-08 14:14 ` James Morris
2005-02-05 9:23 ` Fruhwirth Clemens
2005-02-08 14:48 ` James Morris
2005-02-08 16:08 ` Fruhwirth Clemens
2005-02-08 16:39 ` Fruhwirth Clemens
2005-02-08 23:30 ` James Morris
2005-02-08 23:53 ` Fruhwirth Clemens
2005-02-09 0:09 ` James Morris
2005-02-09 9:14 ` Fruhwirth Clemens
2005-02-10 0:30 ` James Morris
2005-02-10 1:02 ` Fruhwirth Clemens
2005-02-10 1:19 ` Andrew Morton
2005-02-10 1:37 ` Christophe Saout
2005-02-10 9:48 ` Fruhwirth Clemens
2005-02-10 10:33 ` Andrew Morton
2005-02-10 11:17 ` Fruhwirth Clemens
2005-02-10 17:02 ` James Morris
2005-02-10 17:29 ` Fruhwirth Clemens
2005-02-10 17:54 ` James Morris
2005-02-14 13:20 ` Fruhwirth Clemens
2005-02-14 15:56 ` David S. Miller
2005-02-14 17:06 ` Fruhwirth Clemens
2005-02-14 17:07 ` David S. Miller
2005-02-14 17:28 ` Fruhwirth Clemens
2005-02-14 18:16 ` Andrew Morton
2005-02-22 19:16 ` Fruhwirth Clemens
2005-02-12 0:24 ` Matt Mackall
2005-02-10 20:30 ` David S. Miller
2005-02-10 1:42 ` James Morris
2005-02-10 9:50 ` Fruhwirth Clemens
2005-02-02 23:00 ` James Morris
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=20050202153449.1e92c29a.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=clemens@endorphin.org \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@logix.cz \
/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.