public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] Cryptodev support in Core Update 58
Date: Thu, 17 May 2012 18:32:58 +0200	[thread overview]
Message-ID: <1337272378.15371.277.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <CAO6L5t_zZ1=d7GMMvnEwUvDpNh_O7Au6bE73g+KPkgJeujwNkw@mail.gmail.com>

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

Thanks for reviewing that.

Maybe it is a good point to discuss it this article should remain in the
"optimization" section. It is not a guide to manually configure
something and get some more performance out of it.

I feel that this is much better kept in the hardware section. Any
opinions on this?

Michael

On Thu, 2012-05-17 at 18:05 +0200, hilmar sandfuehr wrote:
> documentation team here ;-)
> documentation is 'good to read', just changed some phrases
> 
>   hilmar
> 
> 
> 2012/5/7 Michael Tremer <michael.tremer(a)ipfire.org>
>         Hello,
>         
>         Core Update 58 is in its final state and we are now checking
>         for the
>         documentation of the new feature: cryptodev.
>         
>         I created a short wiki site that contains some technical stuff
>         and a
>         notice for all the Geode users out there.
>         
>         I would like the Documentation team to create a German
>         translation and
>         check on the English version (spelling and maybe make it a bit
>         more
>         user-friendly).
>         
>         http://wiki.ipfire.org/en/optimization/cryptodev
>         
>         This is currently blocking the release of Core Update 58.
>         Therefore I
>         would be glad if you could get this done quickly.
>         
>         Michael
>         
>         _______________________________________________
>         Documentation mailing list
>         Documentation(a)lists.ipfire.org
>         http://lists.ipfire.org/mailman/listinfo/documentation
> 


       reply	other threads:[~2012-05-17 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAO6L5t_zZ1=d7GMMvnEwUvDpNh_O7Au6bE73g+KPkgJeujwNkw@mail.gmail.com>
2012-05-17 16:32 ` Michael Tremer [this message]
     [not found] <4FA8D395.1020203@directbox.de>
2012-05-08 10:52 ` Michael Tremer
2012-05-07 20:11 Michael Tremer

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=1337272378.15371.277.camel@rice-oxley.tremer.info \
    --to=michael.tremer@ipfire.org \
    --cc=documentation@lists.ipfire.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