Linux backports project
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
	"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: [PATCH] backport: allow compilation with Ubuntu's 3.13
Date: Wed, 20 May 2015 18:59:56 +0200	[thread overview]
Message-ID: <1432141196.19214.20.camel@sipsolutions.net> (raw)
In-Reply-To: <555CBC12.4020800@lwfinger.net> (sfid-20150520_185342_445170_F8450E35)

On Wed, 2015-05-20 at 11:53 -0500, Larry Finger wrote:
> On 05/20/2015 11:42 AM, Grumbach, Emmanuel wrote:
> >
> > Good question... I don't know. OTOH, distros don't really support
> > backport. You can't really blame them if they break backport, why should
> > they care?
> > I agree. It is annoying. We can try to convince them, but I don't think
> > that saying "you are all wrong" is the right path. Maybe we should try
> > to have them more involved in backport to fix it themselves?
> > And explain to them how important it is to be able to run backport on
> > top of all their shipped kernels?
> 
> Supporting backport would be a first step, but that won't help all of the rtl8* 
> repos that I have at GitHub. Most of those do not have drivers in the kernel, 
> thus the users are dependent on that kind of external repo; however, I do not 
> have any desire to find out what macro needs to be tested so that these drivers 
> will build on distros that I do not use.

Maybe you could just use backports for those drivers?

johannes


  parent reply	other threads:[~2015-05-20 17:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 13:42 [PATCH] backport: allow compilation with Ubuntu's 3.13 Emmanuel Grumbach
2015-05-20  8:27 ` Johannes Berg
2015-05-20  8:31   ` Grumbach, Emmanuel
2015-05-20  8:34     ` Johannes Berg
2015-05-20  8:39       ` Grumbach, Emmanuel
2015-05-20 15:30         ` Larry Finger
2015-05-20 16:42           ` Grumbach, Emmanuel
2015-05-20 16:53             ` Larry Finger
2015-05-20 16:55               ` Grumbach, Emmanuel
2015-05-20 16:59               ` Johannes Berg [this message]
2015-06-08 18:58           ` Luis R. Rodriguez
2015-06-08 19:00             ` Luis R. Rodriguez
2015-05-20  8:36     ` Luca Coelho
2015-05-25 21:52 ` Hauke Mehrtens
2015-06-08  8:17   ` Luca Coelho
2015-06-08  8:25     ` Coelho, Luciano

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=1432141196.19214.20.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=backports@vger.kernel.org \
    --cc=emmanuel.grumbach@intel.com \
    /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