From: Alexey Dobriyan <adobriyan@gmail.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Kevin Curtis <kevin.curtis@farsite.co.uk>
Subject: [PATCH] farsync: schedule struct fstioc_info::kernelVersion for removal
Date: Wed, 10 Aug 2005 00:03:42 +0400 [thread overview]
Message-ID: <20050809200342.GB10945@mipter.zuzino.mipt.ru> (raw)
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
---
Documentation/feature-removal-schedule.txt | 8 ++++++++
1 files changed, 8 insertions(+)
--- linux-vanilla/Documentation/feature-removal-schedule.txt
+++ linux-farsync/Documentation/feature-removal-schedule.txt
@@ -121,6 +121,14 @@ Who: Grant Coady <gcoady@gmail.com>
---------------------------
+What: struct fstioc_info::kernelVersion used in FSTGETCONF ioctl
+When: November 2005
+Files: drivers/net/wan/farsync.c, drivers/net/wan/farsync.h
+Why: Duplicates uname(2).
+Who: Alexey Dobriyan <adobriyan@gmail.com>
+
+---------------------------
+
What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl])
When: November 2005
Files: drivers/pcmcia/: pcmcia_ioctl.c
reply other threads:[~2005-08-09 19:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050809200342.GB10945@mipter.zuzino.mipt.ru \
--to=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=kevin.curtis@farsite.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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 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).