From: Johan Hovold <johan@kernel.org>
To: Julia Lawall <julia.lawall@inria.fr>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Alex Elder <elder@ieee.org>,
pavankumaryalagada@gmail.com, greybus-dev@lists.linaro.org,
linux-staging@lists.linux.dev, outreachy@lists.linux.dev,
elder@kernel.org, gregkh@linuxfoundation.org,
vaibhav.sr@gmail.com, mgreer@animalcreek.com, vireshk@kernel.org,
rmfrfs@gmail.com, dtwlin@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: Replace format specifiers
Date: Thu, 22 Oct 2026 15:52:41 +0200 [thread overview]
Message-ID: <atoVKX09VDnak7EZ@hovoldconsulting.com> (raw)
In-Reply-To: <6b5a87f-3ca-ddc4-1ea8-f3ee7f45d83@inria.fr>
On Thu, Oct 22, 2026 at 09:45:51AM -0400, Julia Lawall wrote:
> On Thu, 22 Oct 2026, Alex Elder wrote:
> > On 10/22/26 8:35 AM, Julia Lawall wrote:
> > > Does anyone on the greybus list know anything about this person:
> > >
> > > Bryan O'Donoghue <pure.logic@nexus-software.ie>
> > >
> > > The email address is not valid, which is somewhat tiresome...
> >
> > Bryan was on the Greybus kernel team. Remove that address from
> > the list. I'll let him know that e-mail is bouncing so he can
> > add himself back.
>
> Actually, the email comes from the MAINTAINERS file.
Hmm. I haven't seen any such bounces (and I CC:ed that address a couple
of hours ago).
Bryan, is your nexus-software address still valid?
Johan
next prev parent reply other threads:[~2026-10-22 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 16:34 [PATCH] staging: greybus: Replace format specifiers pavankumaryalagada
2026-10-22 13:16 ` Alex Elder
2026-10-22 13:30 ` Julia Lawall
2026-10-23 17:24 ` Yalagada Pavan Kumar
2026-10-24 14:14 ` Alex Elder
2026-10-22 13:35 ` Julia Lawall
2026-10-22 13:41 ` Alex Elder
2026-10-22 13:45 ` Julia Lawall
2026-10-22 13:52 ` Johan Hovold [this message]
2026-10-23 2:30 ` Bryan O'Donoghue
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=atoVKX09VDnak7EZ@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=dtwlin@gmail.com \
--cc=elder@ieee.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mgreer@animalcreek.com \
--cc=outreachy@lists.linux.dev \
--cc=pavankumaryalagada@gmail.com \
--cc=rmfrfs@gmail.com \
--cc=vaibhav.sr@gmail.com \
--cc=vireshk@kernel.org \
/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.