From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Yoichi Yuasa <yuasa@linux-mips.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org
Subject: Re: [PATCH REPOST] pcmcia: Remove NEC VRC4173 CARDU
Date: Fri, 4 Dec 2020 20:20:09 +0100 [thread overview]
Message-ID: <20201204192009.46w4doqoqqvhgrnh@linutronix.de> (raw)
In-Reply-To: <20201119170622.yan5bt2chxvoxqgn@linutronix.de>
On 2020-11-19 18:06:24 [+0100], To linux-kernel@vger.kernel.org wrote:
> On 2020-11-13 22:34:08 [+0100], To linux-kernel@vger.kernel.org wrote:
> > This driver is the very definition of bitrotting:
> > - Introduced in commit
> > 79a140932c776 ("[PATCH] mips: vR41xx updates")
> > which is 2.6.11-rc3.
> >
> > - Provides ->register_callback which was removed in commit
> > 7f316b033b36a ("[PATCH] pcmcia: remove socket register_callback")
> > which is v2.6.14-rc3
> >
> > - Uses INIT_WORK() with three arguments which was removed in commit
> > 65f27f38446e1 ("WorkStruct: Pass the work_struct pointer instead of context data")
> > which is v2.6.20-rc1
> >
> > - Provides ->inquire_socket and uses socket_cap_t which was removed in
> > commit
> > b7949fdacbe00 ("[PCMCIA] Remove inquire_socket")
> > which is 2.5.72
> >
> > - Provides ->get_io_map which was removed in commit
> > d7de1b64a23b9 ("[PCMCIA] pcmcia-2: Remove get_io_map and get_mem_map socket methods.")
> > which is 2.5.66
> >
> > Remove VRC4173 CARDU from the tree because it never had the luck to be
> > successfully compiled. Let it finally find peace in byte heaven.
> …
> > This is a repost of
> > https://lkml.kernel.org/r/20201001193234.gi6fp4vk3dypwifv@linutronix.de
> >
> > which was a repost of
> > https://lkml.kernel.org/r/20200916081629.cfi6svr3yjvzimqs@linutronix.de
>
> Andrew, are you okay with routing this via your tree?
> Nobody responded to this and as I documented in the patch description it
> never compiled so.
Andrew, any chance?
Sebastian
next prev parent reply other threads:[~2020-12-04 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 21:34 [PATCH REPOST] pcmcia: Remove NEC VRC4173 CARDU Sebastian Andrzej Siewior
2020-11-19 17:06 ` Sebastian Andrzej Siewior
2020-12-04 19:20 ` Sebastian Andrzej Siewior [this message]
2020-12-05 8:56 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2020-10-01 19:32 Sebastian Andrzej Siewior
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=20201204192009.46w4doqoqqvhgrnh@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=yuasa@linux-mips.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;
as well as URLs for NNTP newsgroup(s).