From: Andrew Lunn <andrew@lunn.ch>
To: michael@fritscher.net
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net 14/18] drivers: net: xircom: xirc2ps: Remove this driver
Date: Wed, 22 Apr 2026 15:09:00 +0200 [thread overview]
Message-ID: <45d48a34-e40a-43cc-925a-6734149236de@lunn.ch> (raw)
In-Reply-To: <e36510873a1909a1bfd9a05cde99fef0@fritscher.net>
> thanks! If someone mentors me I could try... I have experience with C
> programming, esp. in the embedded world, but (almost) no experience with the
> Linux kernel development.
> But regression tests etc. can be conducted by me - on 32 and 64 bit
> machines. The oldest being a P120, the newest the mentioned X61 with its C2D
> CPU.
For a driver like this, regression testing is mostly what we need,
when we see patches for it.
Please take a look at the MAINTAINERs file, and see if you can send us
a patch adding yourself as the Maintainer of this driver.
Some documents to read:
https://docs.kernel.org/process/submitting-patches.html
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
For patches to MAINTAINERS, please base the patch on net.
Andrew
next prev parent reply other threads:[~2026-04-22 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 6:21 [PATCH net 14/18] drivers: net: xircom: xirc2ps: Remove this driver Michael Fritscher
2026-04-22 12:15 ` Andrew Lunn
2026-04-22 12:46 ` michael
2026-04-22 13:09 ` Andrew Lunn [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-21 19:31 [PATCH net 00/18] Remove a number of ISA and PCMCIA Ethernet drivers Andrew Lunn
2026-04-21 19:31 ` [PATCH net 14/18] drivers: net: xircom: xirc2ps: Remove this driver Andrew Lunn
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=45d48a34-e40a-43cc-925a-6734149236de@lunn.ch \
--to=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@fritscher.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox