linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Christian Brauner <brauner@kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
	bpf@vger.kernel.org, lwn@lwn.net
Cc: lsf-pc@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: LSF/MM/BPF: 2026: Call for Proposals
Date: Wed, 25 Feb 2026 19:52:40 -0700	[thread overview]
Message-ID: <0cbf0f20-e374-4360-8dbb-1f9536774c31@nvidia.com> (raw)
In-Reply-To: <20260224-sangen-aufatmen-06ba16719f33@brauner>

On 2/24/26 2:53 AM, Christian Brauner wrote:
>> Don't forget to pester^wask^wremind your respective organizations to
>> sponsor LSF/MM/BPF 2026! If it helps, you can tell them that we're
>> considering renaming it LSF/MM/BPF/AI.
> 
> I have just looked at the sponsorship site for LSF/MM/BPF/AI again and

Logos only show up there after the sponsorship agreement is completed.
If you are on the LSF/MM committee and are wondering what sponsorships
are really in the pipeline, then I'd recommend checking with your
Linux Foundation contacts, they might be allowed to tell you what is
in the pipeline (maybe?).

In particular, I've been handling the NVIDIA sponsorships for LSF/MM
since 2017, we've done it every year, and we're doing it again this
this year as well.

But it's still getting signed and finalized, so you won't see the
logo up on the LSF/MM page yet. Soon.


thanks,
-- 
John Hubbard

> we all really need to go out and go steal some of that AI funding money
> and funnel it into one of the conferences that really drives development
> of the operating system that drives the compute for all of this.
> 
> Please go and remind your organizations to sponsor. They should know how
> to get in touch with the Linux Foundation. Just going by the sponsorship
> page we're missing a bunch of large organizations that we would
> appreciate if they decided to pitch in. :)
> 
> Christian
> 





  parent reply	other threads:[~2026-02-26  2:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-10 13:24 Christian Brauner
2026-01-19 14:26 ` Christian Brauner
2026-01-29 16:13   ` Christian Brauner
2026-02-16 14:25     ` Christian Brauner
2026-02-17 10:37       ` Haris Iqbal
2026-02-18  9:56         ` Christian Brauner
2026-02-24  9:53       ` Christian Brauner
2026-02-24 13:37         ` James Bottomley
2026-02-26  2:52         ` John Hubbard [this message]
2026-01-22  3:22 ` Al Viro
2026-01-23 10:16   ` Christian Brauner
2026-02-25 14:52 ` LSF/MM/BPF: 2026: (V)FS: First Round of Invites Sent Christian Brauner

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=0cbf0f20-e374-4360-8dbb-1f9536774c31@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=bpf@vger.kernel.org \
    --cc=brauner@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=lwn@lwn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox