mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Joel Fernandes <joelagnelf@nvidia.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	 John Hubbard <jhubbard@nvidia.com>,
	linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
	 rust-for-linux <rust-for-linux@vger.kernel.org>,
	nouveau@lists.freedesktop.org,  Boqun Feng <boqun.feng@gmail.com>,
	Paul E McKenney <paulmck@kernel.org>,
	 Jason Gunthorpe <jgg@nvidia.com>,
	rostedt@google.com, Yury Norov <yury.norov@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: Update email address for Joel Fernandes
Date: Wed, 7 Jan 2026 18:38:00 +0100	[thread overview]
Message-ID: <CANiq72k6xengESGrJSELV8OtOwaO2d-DO0_to=WCu8PtfhH3mQ@mail.gmail.com> (raw)
In-Reply-To: <20260107123159.7ac61d69@gandalf.local.home>

On Wed, Jan 7, 2026 at 6:31 PM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> This is why I prefer the "(company)" in the email name and not the address.
> It allows developers to maintain the same email while they move companies.
> I did this for Red Hat, VMware and now Google, and all with the same email
> address.

Yeah, it is simpler for everyone else, indeed.

> Although I may need to switch to my kernel.org address because my
> goodmis.org is being blocked by gmail :-p

I saw your post in LinkedIn about the pain... :)

But yeah, so far kernel.org is smooth (knocking on wood).

Cheers,
Miguel

  reply	other threads:[~2026-01-07 17:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05  0:30 Joel Fernandes
2026-01-06  3:22 ` John Hubbard
2026-01-06 10:42   ` Joel Fernandes
2026-01-07 12:46     ` Miguel Ojeda
2026-01-07 17:20       ` Joel Fernandes
2026-01-07 17:24         ` Miguel Ojeda
2026-01-07 18:44           ` Joel Fernandes
2026-01-07 17:31         ` Steven Rostedt
2026-01-07 17:38           ` Miguel Ojeda [this message]
2026-01-07 18:44           ` Joel Fernandes

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='CANiq72k6xengESGrJSELV8OtOwaO2d-DO0_to=WCu8PtfhH3mQ@mail.gmail.com' \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=jgg@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=joel@joelfernandes.org \
    --cc=joelagnelf@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=rostedt@google.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=yury.norov@gmail.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

all inboxes | Powered by JetHome®