public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Justin Clift <justin@postgresql.org>
To: James Morris <jmorris@intercode.com.au>
Cc: Andrew McGregor <andrew@indranet.co.nz>,
	linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@redhat.com>,
	cryptoapi-devel <cryptoapi-devel@kerneli.org>
Subject: Re: [CryptoAPI-devel] Re: [RFC] Hardware support notes for the kernel crypto API (2.5+)
Date: Sun, 15 Dec 2002 15:34:23 +1100	[thread overview]
Message-ID: <3DFC064F.10708@postgresql.org> (raw)
In-Reply-To: Mutt.LNX.4.44.0212151210450.30004-100000@blackbird.intercode.com.au

James Morris wrote:
> On Sun, 15 Dec 2002, Andrew McGregor wrote:
> 
> 
>>But OpenBSD has drivers, and they say that Broadcom were very good to deal 
>>with.  I suggest writing the OpenBSD driver maintainer and asking who to 
>>contact.
> 
> 
> The OpenBSD developer said he's given up talking to Broadcom and declined
> to provide the email address of his contact.
> 
> Although I'm sure we can work something out if we can actually find the
> right person to talk to.


Ok, just filled out a request form on their site, asking them who the best person for us to contact is.

***********

Hello,

Is Broadcom interested in having support for their encryption acceleration products (not just the one given in the 
product number above) officially added to Linux?

The Linux "CryptoAPI" project is trying to find out the best person at Broadcom to contect, as we are adding support for 
encryption hardware to the Linux kernel and are wondering you guys would like your products included.

:-)

Regards and best wishes,

Justin Clift

***********

Reckon we should probably hear something back within 3-4 days.  It's worded clearly enough for pretty much anyone there 
to understand, and gives them a solid "reason to contact us" back.

:-)

Does it sound ok?

Regards and best wishes,

Justin Clift


> - James


-- 
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi


  reply	other threads:[~2002-12-15  4:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Mutt.LNX.4.44.0212150025190.24712-100000@blackbird.intercode.co m.au>
2002-12-14 13:51 ` [RFC] Hardware support notes for the kernel crypto API (2.5+) James Morris
2002-12-14 21:28   ` Andrew McGregor
2002-12-15  1:15     ` James Morris
2002-12-15  4:34       ` Justin Clift [this message]
2002-12-17 16:54         ` [CryptoAPI-devel] " Jean-Luc Cooke
2002-12-17  0:15   ` [CryptoAPI-devel] " Steve Isaacs
2002-12-17  0:56   ` Steve Isaacs

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=3DFC064F.10708@postgresql.org \
    --to=justin@postgresql.org \
    --cc=andrew@indranet.co.nz \
    --cc=cryptoapi-devel@kerneli.org \
    --cc=davem@redhat.com \
    --cc=jmorris@intercode.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /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