linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: hauke@hauke-m.de, kernel-team@lists.ubuntu.com,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] compat: add compat kernel checker and downloader
Date: Mon, 6 Feb 2012 11:07:28 -0500	[thread overview]
Message-ID: <20120206160727.GA21048@tuxdriver.com> (raw)
In-Reply-To: <1328312594-31934-1-git-send-email-mcgrof@frijolero.org>

On Fri, Feb 03, 2012 at 03:43:14PM -0800, Luis R. Rodriguez wrote:
> This adds get-compat-kernels, a utility that is intended
> to be Linux distribution agnostic that downloads and installs
> all kernel headers for all supported kernel releases of compat.
> You also have the option of specifying you want to also install
> the actual kernel image (get-compat-kernels -i).
> 
> We start off by adding support for Ubuntu on x86_64 as that
> is what a few of us maintaining compat and compat-wireless run.
> Just for kernel headers (default run of get-compat-kernels),
> you'll need currently 205 M of hard drive space.
> 
> Once done with running get-compat-kernels, you can then
> start running ckmake to verify your compat kernel changes
> won't bust compilation against any known supported kernel.
> 
> I'd like to start requiring runs against this script for
> patch submissions. Eventually we can try to add the same
> runs against compat-wireless so we can verify integrity
> against compilation for different kernel versions.
> 
> Support for different Linux distributios is welcomed.
> 
> Debug log goes out to ckmake.log
> 
> Example output:
> 
> mcgrof@tux ~/compat (git::master)$ ckmake
> Trying kernel                  3.3.0-030300rc2-generic  [OK]
> Trying kernel                     3.2.2-030202-generic  [OK]
> Trying kernel                    3.1.10-030110-generic  [OK]
> Trying kernel                    3.0.18-030018-generic  [OK]
> Trying kernel                  2.6.39-02063904-generic  [OK]
> Trying kernel                         2.6.38-8-generic  [OK]
> Trying kernel                        2.6.38-13-generic  [OK]
> Trying kernel                        2.6.38-12-generic  [OK]
> Trying kernel                        2.6.38-11-generic  [OK]
> Trying kernel                        2.6.38-10-generic  [OK]
> Trying kernel                  2.6.38-02063808-generic  [OK]
> Trying kernel                  2.6.37-02063706-generic  [OK]
> Trying kernel                  2.6.36-02063604-generic  [OK]
> Trying kernel                  2.6.35-02063512-generic  [OK]
> Trying kernel                  2.6.34-02063410-generic  [OK]
> Trying kernel                  2.6.33-02063305-generic  [OK]
> Trying kernel                  2.6.32-02063255-generic  [OK]
> Trying kernel                        2.6.31-22-generic  [OK]
> Trying kernel                  2.6.31-02063113-generic  [OK]
> Trying kernel                  2.6.30-02063010-generic  [OK]
> Trying kernel                  2.6.29-02062906-generic  [OK]
> Trying kernel                  2.6.28-02062810-generic  [OK]
> Trying kernel                    2.6.27-020627-generic  [OK]
> Trying kernel                    2.6.26-020626-generic  [OK]
> Trying kernel                    2.6.25-020625-generic  [OK]
> Trying kernel                    2.6.24-020624-generic  [OK]
> 
> Cc: kernel-team@lists.ubuntu.com
> Signed-off-by: Luis R. Rodriguez <mcgrof@frijolero.org>

I'm not sure this makes any sense.  I thought the point of the compat
project was to support upstream kernels, not distro ones?  I'm not
even sure I know how to replicate the above process in Fedora, since
we would only have kernels available from a given release in each
release's repository.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  parent reply	other threads:[~2012-02-06 16:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 23:43 [PATCH] compat: add compat kernel checker and downloader Luis R. Rodriguez
2012-02-06 10:57 ` Andy Whitcroft
2012-02-06 16:07 ` John W. Linville [this message]
2012-02-07  4:19   ` Luis R. Rodriguez
2012-02-07  4:56     ` Luis R. Rodriguez
2012-02-08  1:19       ` Luis R. Rodriguez
2012-02-08  2:55         ` Luis R. Rodriguez
2012-02-08  2:58           ` Luis R. Rodriguez
2012-03-31  0:23             ` Luis R. Rodriguez
2012-04-04 11:10               ` Andy Whitcroft
2012-04-05 20:19                 ` Tim Gardner

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=20120206160727.GA21048@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=hauke@hauke-m.de \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@frijolero.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;
as well as URLs for NNTP newsgroup(s).