On Sat, 2011-04-23 at 22:56 +0530, Faheem Mitha wrote:
> 
> On Sat, 23 Apr 2011, Faheem Mitha wrote:
> 
> > I've made some more changes - mostly additions - to your patch.
> [snippage]
> 
> Oops, I accidentally included some redundant stuff. Resending
> corrected patch.
> 
>                                                Regards, Faheem
> 
> diff -r 657cba972ce9 -r 4f9540ff7c84 chapter-common-tasks.sgml
> --- a/chapter-common-tasks.sgml       Mon Apr 18 11:54:22 2011 +0530
> +++ b/chapter-common-tasks.sgml       Sat Apr 23 22:53:06 2011 +0530
[...]
> @@ -104,6 +104,60 @@
>           (featuresets added).  You should apply the extra patches in
>           the appropriate subdirectory.
>         </p>
> +       <p>
> +         To change the configuration before building, for example
> +         for the 686-bigmem flavour on i386, run the commands:
> +         <example>
> +$ fakeroot make -f debian/rules.gen setup_i386_none_686-bigmem
> +$ make -C debian/build/build_i386_none_686-bigmem menuconfig
> +         </example>
> +       </p>
> +       <p>
> +         Patches or configuration changes to the kernel may alter
> +         the kernel Application Binary Interface (ABI).
> +       </p>
> +       <p>
> +            If an exported function is conditional on CONFIG_FOO, or
> +            it uses a type whose definition depends on CONFIG_FOO,
> +            then turning CONFIG_FOO on or off changes the ABI of that
> +            function, and thus of the kernel as a whole.
> +       </p>
> +       <p>
> +         Enabling or changing the configuration of a single driver
> +         usually doesn't change the ABI, because most drivers don't
> +         export anything.
> +       </p>
[...]

I think this is just too much detail for this section.  If you think
it's necessary to explain ABI maintenance in this much detail, that
probably belongs in a new chapter.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to