From: Simon Deziel <simon@sdeziel.info>
To: wireguard@lists.zx2c4.com
Subject: Re: Ubuntu kernel >= 5.3.0-52.46 breaks DKMS build for wireguard-linux-compat >= 1.0.20200429, patch included
Date: Wed, 6 May 2020 12:22:48 -0400 [thread overview]
Message-ID: <d62b74e0-0ae7-4948-df6d-325bcef94112@sdeziel.info> (raw)
In-Reply-To: <CAHmME9rnxp2QYjhu1vU+2K1GaoM2hupz5uJGpo_8z4t=E2-boQ@mail.gmail.com>
On 2020-05-05 12:03 a.m., Jason at zx2c4.com (Jason A. Donenfeld) wrote:
>> Note that as of now, 5.3.0-51.44 is still the latest "official" HWE
>> kernel for 18.04, and 5.3.0-52.46 is only available from Ubuntu's
>> "bionic-proposed" repo.
>
> Ahh, you're running -proposed, gotcha. So I guess I should wait until
> this hits the main repo. Any idea when they usually do that?
The next kernel batch should land in -updates on May 18th. The detailed
schedule is at https://kernel.ubuntu.com/
Regards,
Simon
next prev parent reply other threads:[~2020-05-07 0:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 20:33 Pascal Ernster
2020-05-05 1:37 ` Jason A. Donenfeld
2020-05-05 3:52 ` Pascal Ernster
2020-05-05 4:03 ` Jason A. Donenfeld
2020-05-05 4:27 ` Pascal Ernster
2020-05-06 16:22 ` Simon Deziel [this message]
2020-05-07 0:29 ` Jason A. Donenfeld
2020-05-20 15:04 ` Vasili Pupkin
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=d62b74e0-0ae7-4948-df6d-325bcef94112@sdeziel.info \
--to=simon@sdeziel.info \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).