From: Al <awvger@sunnyside.com>
To: linux-hams@vger.kernel.org
Subject: Re: [PATCH] ax25.h unsigned long type for ax25 timers
Date: Thu, 19 Jun 2008 13:35:50 -0700 [thread overview]
Message-ID: <485AC326.6000709@sunnyside.com> (raw)
In-Reply-To: <485AB5A2.20806@sunnyside.com>
Actually on closer inspection, the items are reordered, which would
break existing compiled programs, so I'll have to reverse myself on this.
Sorry for the distraction.
Al
Al wrote:
> David
> My impression was that the proposed change did NOT change binary
> interfaces to the kernel, but correctly labeled fields for the first
> time specifically as "long" instead of the fuzzy definition as "int".
> While it's true that a non-386 system where "int" is not a "long"
> would be adversely affected, there appear not to be any of those
> (rare) systems running this software, so the point seems entirely moot.
> The proposed change improves strict type checking and makes a cleaner
> definition.
> I say let it in.
> Al
>
> David Miller wrote:
>> From: Bernard Pidoux <bpidoux@free.fr>
>> Date: Tue, 17 Jun 2008 15:04:38 +0200
>>
>>
>>> In linux/include/linux/ax25.h
>>> ax25_info_struct timers types remain unsigned
>>>
>>> struct ax25_info_struct {
>>> unsigned int n2, n2count;
>>> unsigned int t1, t1timer;
>>> unsigned int t2, t2timer;
>>> unsigned int t3, t3timer;
>>> unsigned int idle, idletimer;
>>> .....
>>> };
>>>
>>> while in linux/include/net/ax25.h timers are unsigned long according
>>> to kernel 2.6 timers.
>>>
>>> typedef struct ax25_cb {
>>> .....
>>> struct timer_list t1timer, t2timer, t3timer, idletimer;
>>> unsigned long t1, t2, t3, idle, rtt;
>>> ....
>>>
>>> Although ax25_info_struct is not much used it is refered at least
>>> into libax25 and xfbb BBS application program.
>>>
>>> It seems thus reasonable to make the change.
>>>
>>> Signed-off-by: Bernard Pidoux <f6bvp@amsat.org>
>>>
>>
>> Unfortunately this datastructure is exported to userspace,
>> and therefore we cannot change the structure layout without
>> breaking userspace.
>>
>> We cannot, as a result, make this change.
>>
>> The only way to fix this is to make a new fixed structure, and add new
>> ax25 calls that accept this new structure.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2008-06-19 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 13:04 [PATCH] ax25.h unsigned long type for ax25 timers Bernard Pidoux
2008-06-18 5:30 ` David Miller
2008-06-19 16:28 ` Bernard Pidoux
2008-06-19 21:46 ` David Miller
2008-06-19 22:38 ` Bernard Pidoux
2008-06-20 13:17 ` Bernard Pidoux F6BVP
2008-06-28 2:33 ` David Miller
2008-06-19 19:38 ` Al
2008-06-19 20:35 ` Al [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=485AC326.6000709@sunnyside.com \
--to=awvger@sunnyside.com \
--cc=linux-hams@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