Linux backports project
 help / color / mirror / Atom feed
From: Andy Gospodarek <andy@greyhouse.net>
To: Phil Perry <phil@pendre.co.uk>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [ANN] new backports project
Date: Thu, 4 Apr 2013 21:52:29 -0400	[thread overview]
Message-ID: <20130405015229.GL27415@gospo.rdu.redhat.com> (raw)
In-Reply-To: <515B4994.3030309@pendre.co.uk>

On Tue, Apr 02, 2013 at 10:11:48PM +0100, Phil Perry wrote:
> On 02/04/13 18:20, Johannes Berg wrote:
> >
> >>  * Redhat kernel backport support -- this should be fairly easy
> >
> 
> I too am very interested in support for RHEL.
> 
> We had support up to date for compat-wireless-3.5 under RHEL-6.3.
> 
> Unsurprisingly the release of RHEL-6.4 broke a whole load of stuff
> given the amount of backporting RH did into their kernel (I believe
> they backported the wireless stack from ~ kernel-3.5 into their
> kernel).
> 
> I (and a colleague) played with compat-drivers-2013-03-07-u.tar.bz2
> to get alx to build under RHEL-6.4 but I never got as far as looking
> at building everything. The seemingly endless cycle of breakage on
> every RHEL release and having to fix it kind of left me losing the
> will to keep fixing it, especially as for the moment the RHEL kernel
> has a relatively recent wireless driver stack. Any solution that
> might ease this break and fix cycle would be very welcome here.

I'm glad to hear the use of compat-wireless is at least moderately
useful on RHEL6.  A few of us have an interest in keeping compat going
on RHEL6, but none had the cycles to get compat.git fixed-up before 6.4
was released.  I'm actually in the process of posting patches for 6.3.z
as someone had created an upstream bugzilla for this, so I would
encourage anyone who wants it working on 6.4 to do the same.

> >I addressed this, but I'm unsure of it and don't have a way to test it,
> >so any testing would be appreciated (as it is in general, of course)
> >
> 
> I've not looked closely at what you've done, but I have an interest
> in building/packaging compat-drivers for RHEL and can possibly help
> test. If you have a snapshot that you think should build on RHEL or
> that I could use as a starting point?
> 

I would also like to see this -- though I guess I can probably just
clone the git repo and check it out.


      parent reply	other threads:[~2013-04-05  1:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 13:19 [ANN] new backports project Johannes Berg
2013-04-02 16:35 ` Norman Shulman
2013-04-02 17:20 ` Johannes Berg
2013-04-02 19:04   ` Luis R. Rodriguez
2013-04-02 21:11   ` Phil Perry
2013-04-02 21:23     ` Johannes Berg
2013-04-02 21:42       ` Luis R. Rodriguez
2013-04-05  2:12         ` Andy Gospodarek
2013-04-05  2:29           ` Luis R. Rodriguez
2013-04-05 10:12             ` Johannes Berg
2013-04-05 14:17               ` Johannes Berg
2013-04-05  1:52     ` Andy Gospodarek [this message]

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=20130405015229.GL27415@gospo.rdu.redhat.com \
    --to=andy@greyhouse.net \
    --cc=backports@vger.kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=phil@pendre.co.uk \
    /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