Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Simon Deziel <simon@sdeziel.info>, unit193@ubuntu.com
Cc: WireGuard mailing list <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 18:29:13 -0600	[thread overview]
Message-ID: <CAHmME9qwfUTvEHHG6b3K3eGUiGZ7iyoD2VmX-tomz7tWTwT4TQ@mail.gmail.com> (raw)
In-Reply-To: <d62b74e0-0ae7-4948-df6d-325bcef94112@sdeziel.info>

On Wed, May 6, 2020 at 6:27 PM Simon Deziel <simon@sdeziel.info> wrote:
>
> 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/

Ooof, thanks for that info. Looks like we're a tad early on the .52 changes.

  reply	other threads:[~2020-05-07  0:29 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
2020-05-07  0:29         ` Jason A. Donenfeld [this message]
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=CAHmME9qwfUTvEHHG6b3K3eGUiGZ7iyoD2VmX-tomz7tWTwT4TQ@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=simon@sdeziel.info \
    --cc=unit193@ubuntu.com \
    --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).