On Nov 17, 2007 7:49 PM, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote: > > to show what goes into a composite module. but if you look at that > cifs entry above, it uses "cifs-y" instead. my question was whether > those two techniques are exactly equivalent. look at the difference > between the rio entry and the cifs entry (both pulled verbatim out of > the tree), and tell me if there's a reason they use different > techniques to define the composite object. > To requote the text from the documentation: Kbuild recognises objects used for composite objects by the suffix -objs, and the suffix -y. And from the above one sentence, my answer (just logical answer, correct if I am wrong) to your question is YES. They are the same - because of the word "and"??? But documentation is correct or not does not matter - what matters is it working in real life? Is the two the same in real life? I got no experience yet. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
