From: Bernd Schubert <bernd-schubert@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: API changes / 2.6.21 sysctl changes
Date: Mon, 11 Jun 2007 15:13:12 +0200 [thread overview]
Message-ID: <200706111513.12998.bernd-schubert@gmx.de> (raw)
Hi,
in 2.6.21 register_sysctl_table(), struct ctl_table and probably something
else did change. Unfortunately so far I didn't figure out the "something
else".
Please, if generic interface modifications render all available documentation
in the web invalid, is it so hard to also write kernel api documentation then
(even if it so far does not exist in the Documentation/ dir)?
I mean the time overhead of thousands of coders digging through git commits is
huge, just because API changes are not properly documented.
E.g.: Documentation/api/sysctl.txt
Up to 2.6.20:
struct ctl_table_header *register_sysctl_table(ctl_table * table, int
insert_at_head);
Beginning with 2.6.21-rcX:
struct ctl_table_header *register_sysctl_table(ctl_table * table);
struct ctl_table:
removed entry struct proc_dir_entry *de
added entry ctl_table *parent
[Maybe also something like]
Additionaly to different functions calls, programmers also need to change ...
Thanks,
Bernd
Thanks,
Bernd
next reply other threads:[~2007-06-11 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 13:13 Bernd Schubert [this message]
2007-06-11 15:46 ` Alexey Dobriyan
2007-06-11 15:59 ` Bernd Schubert
2007-06-11 16:41 ` Alexey Dobriyan
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=200706111513.12998.bernd-schubert@gmx.de \
--to=bernd-schubert@gmx.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®