All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Johannes Berg <johannes@sipsolutions.net>, backports@vger.kernel.org
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: Dealing with SUBLEVEL overflow in backports
Date: Mon, 7 Feb 2022 12:52:02 +0000	[thread overview]
Message-ID: <5a58d473-a0a1-b213-c71d-963e6b180593@flygoat.com> (raw)
In-Reply-To: <bb0ae37aa770e016463706d557fec1c5205bc6a9.camel@sipsolutions.net>



在 2022/2/7 11:11, Johannes Berg 写道:
>
> Looking at commit b29eec6c49, does it even matter? We can continue using
> bug.h which includes build_bug.h, it's just pulling in more than needed.
Sorry, in which tree?

Thanks.
- Jiaxun
>
> johannes

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

  reply	other threads:[~2022-02-07 13:38 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 [this message]
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
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=5a58d473-a0a1-b213-c71d-963e6b180593@flygoat.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=johannes@sipsolutions.net \
    /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.