From: Jakub Kicinski <kuba@kernel.org>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: Stefan Wahren <wahrenst@gmx.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: Re: [PATCH V2 12/12 net-next] qca_7k: Replace old mail address
Date: Tue, 2 Jan 2024 06:58:22 -0800 [thread overview]
Message-ID: <20240102065822.319389ec@kernel.org> (raw)
In-Reply-To: <18c39111-1cee-429d-a9ff-ff98e1ed27dc@intel.com>
On Wed, 20 Dec 2023 15:04:51 -0800 Jacob Keller wrote:
> On 12/18/2023 3:26 PM, Stefan Wahren wrote:
> > From: Stefan Wahren <stefan.wahren@i2se.com>
> >
> > The company I2SE has been acquired a long time ago. Switch to
> > my private mail address before the I2SE account is deactivated.
> >
> > Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> > Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
>
> You might also consider adding this to the .mailmap so that
> contributions from your old i2se.com address would show up to the
> gmx.net address and people might be less likely to try and cc the dead
> address.
Agreed, also - this driver seems to have no MAINTAINERS entry.
Please consider adding yourself as the maintainer :)
prev parent reply other threads:[~2024-01-02 14:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 23:26 [PATCH V2 00/12 net-next] qca_spi: collection of improvements Stefan Wahren
2023-12-18 23:26 ` [PATCH V2 01/12 net-next] qca_spi: Improve SPI thread creation Stefan Wahren
2023-12-20 23:05 ` Jacob Keller
2023-12-18 23:26 ` [PATCH V2 02/12 net-next] qca_spi: Improve SPI IRQ handling Stefan Wahren
2023-12-20 22:21 ` Jacob Keller
2023-12-18 23:26 ` [PATCH V2 03/12 net-next] qca_spi: Avoid skb_copy_expand in TX path Stefan Wahren
2023-12-20 22:22 ` Jacob Keller
2023-12-18 23:26 ` [PATCH V2 04/12 net-next] qca_7k_common: Drop unnecessary function description Stefan Wahren
2023-12-20 22:23 ` Jacob Keller
2023-12-18 23:26 ` [PATCH V2 05/12 net-next] qca_7k_common: Drop unused len from qcafrm_handle Stefan Wahren
2023-12-20 22:23 ` Jacob Keller
2023-12-18 23:26 ` [PATCH V2 06/12 net-next] qca_spi: Add QCASPI prefix to ring defines Stefan Wahren
2023-12-20 22:24 ` Jacob Keller
2023-12-18 23:26 ` [PATCH V2 07/12 net-next] qca_spi: Introduce QCASPI_RX_MAX_FRAMES Stefan Wahren
2023-12-20 22:26 ` Jacob Keller
2023-12-18 23:26 ` [PATCH V2 08/12 net-next] qca_spi: Improve calculation of RX buffer size Stefan Wahren
2023-12-20 23:00 ` Jacob Keller
2023-12-18 23:26 ` [PATCH V2 09/12 net-next] qca_spi: Log expected signature in error case Stefan Wahren
2023-12-20 23:01 ` Jacob Keller
2023-12-18 23:26 ` [PATCH V2 10/12 net-next] qca_spi: Adjust log of SPI_REG_RDBUF_BYTE_AVA Stefan Wahren
2023-12-20 23:02 ` Jacob Keller
2023-12-18 23:26 ` [PATCH V2 11/12 net-next] qca_7k: Replace BSD boilerplate with SPDX Stefan Wahren
2023-12-20 23:02 ` Jacob Keller
2023-12-18 23:26 ` [PATCH V2 12/12 net-next] qca_7k: Replace old mail address Stefan Wahren
2023-12-20 23:04 ` Jacob Keller
2024-01-02 14:58 ` Jakub Kicinski [this message]
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=20240102065822.319389ec@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan.wahren@i2se.com \
--cc=wahrenst@gmx.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;
as well as URLs for NNTP newsgroup(s).