Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] ocf-linux: new package
Date: Sat, 05 May 2012 09:39:21 -0300	[thread overview]
Message-ID: <5e88124f6b69d203ad230db954cd9d4e@zacarias.com.ar> (raw)
In-Reply-To: <87wr4qde8n.fsf@macbook.be.48ers.dk>

On 2012-05-05 09:06, Peter Korsgaard wrote:

> I would move the 'also' - E.G. 'Some libraries need to also have OCF 
> enabled'

Ok.

> How likely is it that this patch will work for a random kernel 
> version?
> From the tarball I see a bunch of patches for different versions, so 
> we
> probably need something smarter than just hardcoding 3.2.1 - Perhaps
> just an option where the user can type the version number of the 
> patch
> they want to use?

Run-tested as low as 2.6.38.x
Build-tested as low as 2.6.35.x
I can give it a run-test on 2.6.35 maybe, depending on how lucky i am 
with my hardware crypto enabled test platforms.

> Trailing spaces (the last empty line).

Fixed.
Let me know regarding the kernel patch what you prefer given the new 
information to avoid sending zillions of versions.
Regards.

  reply	other threads:[~2012-05-05 12:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 19:23 [Buildroot] [PATCH 0/0] OCF-Linux Gustavo Zacarias
2012-05-04 19:23 ` [Buildroot] [PATCH 1/2] ocf-linux: new package Gustavo Zacarias
2012-05-05 12:06   ` Peter Korsgaard
2012-05-05 12:39     ` Gustavo Zacarias [this message]
2012-05-05 12:56       ` Peter Korsgaard
2012-05-05 13:31         ` Gustavo Zacarias
2012-05-04 19:23 ` [Buildroot] [PATCH 2/2] openssl: switch to the ocf-linux package Gustavo Zacarias
  -- strict thread matches above, loose matches on Subject: below --
2012-03-20 13:23 [Buildroot] ocf-linux patchset Gustavo Zacarias
2012-03-20 13:23 ` [Buildroot] [PATCH 1/2] ocf-linux: new package Gustavo Zacarias
2012-03-20 22:36   ` Arnout Vandecappelle

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=5e88124f6b69d203ad230db954cd9d4e@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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