All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	backports@vger.kernel.org
Subject: Re: Dealing with SUBLEVEL overflow in backports
Date: Thu, 10 Feb 2022 09:17:24 +0100	[thread overview]
Message-ID: <7c1fd2554ae907eded15dd247bbda5bc5c28cbe7.camel@sipsolutions.net> (raw)
In-Reply-To: <789b2e40-c0f2-c078-907d-ceeacc8c2da9@hauke-m.de>

On Thu, 2022-02-10 at 00:44 +0100, Hauke Mehrtens wrote:
> 
> What build problem do you get when you include "#include <linux/bug.h>" 
> here on kernel 4.9.299?
> 

I haven't tried, but per the explanation, you get issues if you tried to
include bug.h in the first place, since then you get

bug.h
-> includes build_bug.h (since the patch)
-> uses build_bug.h from backports
-> includes bug.h (does nothing, double include)

and you're then missing the defines from build_bug.h.

> Can we somehow work around this problem by 
> detection the kernel version in a different way based on a different define?
> 

I don't think so. However, I don't yet see why passing the version on
the command line doesn't work, since we only ever need to care about
files we compile?

johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

  parent reply	other threads:[~2022-02-10  8:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  1:19 Dealing with SUBLEVEL overflow in backports Jiaxun Yang
2022-02-07  9:15 ` Johannes Berg
2022-02-07 10:50   ` Johannes Berg
2022-02-07 11:09     ` Jiaxun Yang
2022-02-07 11:11       ` Johannes Berg
2022-02-07 12:52         ` Jiaxun Yang
2022-02-07 13:04           ` Johannes Berg
2022-02-07 13:40             ` Jiaxun Yang
2022-02-07 13:57               ` Johannes Berg
2022-02-07 22:18                 ` Hauke Mehrtens
2022-02-08  7:58                   ` Johannes Berg
2022-02-08 14:50                     ` Jiaxun Yang
2022-02-08 15:02                       ` Johannes Berg
2022-02-08 15:51                         ` Jiaxun Yang
2022-02-09 23:44                           ` Hauke Mehrtens
2022-02-09 23:45                             ` Hauke Mehrtens
2022-02-10  8:17                             ` Johannes Berg [this message]
2022-02-10 14:05                               ` Jiaxun Yang
2022-04-03 23:19                                 ` Hauke Mehrtens
2022-05-04 12:04                                   ` Johannes Berg

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=7c1fd2554ae907eded15dd247bbda5bc5c28cbe7.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=jiaxun.yang@flygoat.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.