Messages in this thread | | | Date | Fri, 2 Dec 2011 09:42:13 +0100 | From | Alessandro Rubini <> | Subject | Re: [RFC PATCH V2 0/1] making order in file2alias |
| |
> But splitting 15-line functions into separate files? Less compact, less > simple.
Personally, I'm more interested in the addition of new busses (as drop-in files) than the split up of current ones. But I see your point.
>> > step 1: create the ELF section so ENTRY() lines can leave the array >> > (and change name accordingly). >> > >> > step 2: each ENTRY() line can be moved just after the associated code >> > (this means that a new bus is just a single hunk, not 2 of them) >> > >> > step 3: I create the headers needed to move code and ENTRY in separate >> > files. This is some movement around, not trivial so it may >> > deserve a patch in itself.
> If you *really* want to use separate files, then this patch will let you > do it. You'll need to expose some stuff in a header though.
Fine with me. This is 1 and 2 of my list above. And the "need to expose" is my step 3. So I agree with this.
thanks /alessandro
| |