From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 23
Date: Thu, 23 Feb 2023 09:22:50 +0100 [thread overview]
Message-ID: <CAMuHMdUa+RiSx1SdKSbYb6mCbQHY6V2oer=awkaWCuHuk1cayQ@mail.gmail.com> (raw)
In-Reply-To: <20230223145519.11eb6515@canb.auug.org.au>
Hi Stephen,
On Thu, Feb 23, 2023 at 5:18 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Merging net/master (5b7c4cabbb65 Merge tag 'net-next-6.3' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next)
> Merging net-next/master (5b7c4cabbb65 Merge tag 'net-next-6.3' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next)
Niklas Söderlund has just made me aware of the following "private"
netdev announcement, which you seem to have missed:
"[ANN] netdev master branches going away tomorrow!"
https://lore.kernel.org/netdev/20230222102946.7912b1b9@kernel.org
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2023-02-23 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 3:55 linux-next: Tree for Feb 23 Stephen Rothwell
2023-02-23 8:22 ` Geert Uytterhoeven [this message]
2023-02-23 9:27 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 4:40 Stephen Rothwell
2022-02-24 1:44 broonie
2021-02-23 6:35 Stephen Rothwell
2018-02-23 3:47 Stephen Rothwell
2017-02-23 5:00 Stephen Rothwell
2016-02-23 5:01 Stephen Rothwell
2015-02-23 3:09 Stephen Rothwell
2013-02-25 5:00 Stephen Rothwell
2013-02-25 5:00 ` Stephen Rothwell
2012-02-23 3:37 Stephen Rothwell
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='CAMuHMdUa+RiSx1SdKSbYb6mCbQHY6V2oer=awkaWCuHuk1cayQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.