All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: [PATCH] backport: allow compilation with Ubuntu's 3.13
Date: Wed, 20 May 2015 10:34:53 +0200	[thread overview]
Message-ID: <1432110893.2174.3.camel@sipsolutions.net> (raw)
In-Reply-To: <1432110664.5612.6.camel@intel.com>

On Wed, 2015-05-20 at 08:31 +0000, Grumbach, Emmanuel wrote:
> On Wed, 2015-05-20 at 10:27 +0200, Johannes Berg wrote:
> > On Tue, 2015-05-19 at 16:42 +0300, Emmanuel Grumbach wrote:
> > 
> > > +#if (LINUX_VERSION_CODE == KERNEL_VERSION(3,13,11) && UTS_UBUNTU_RELEASE_ABI < 24)
> > 
> > Now that I look at this again, I'm confused - shouldn't this whole thing
> > have a ! in front?
> > 
> 
> why?
> I need this definition only for Ubuntu releases that are below 24.
> Canonical ported that starting 24.
> What am I missing?

But every mainline kernel, say 3.10, also needs it. Also Ubuntu with
3.10, for example.

johannes


  reply	other threads:[~2015-05-20  8:34 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 [this message]
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
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=1432110893.2174.3.camel@sipsolutions.net \
    --to=johannes@sipsolutions.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.