Re: module_license tree refreshed against linux-next

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 23 Mar 2023 20:38:02 +0000
Nick Alcock <nick.alcock@xxxxxxxxxx> wrote:

> Oh the name is dreadful! Better name suggestions much appreciated.

And kernel developers are notorious at picking bad names.

> 
> > Perhaps "sym-file" ?  
> 
> ... Yes, except that it also decorates with built-in module names.
> 
> > Or does this happen only when there's more than one function? Either way,
> > let's try to come up with something other than "sym-unambiguous".  
> 
> It happens only when at least one symbol in a given (object file *
> built-in module) pair would be ambiguous with respect to some other
> symbol with the same name without being given at least one of those two.
> It's a bit hard to pack into a couple of words... sym-unique is even
> worse, sym-objname is deeply unclear (what's an objname?) sym-filenames
> maybe? The question really is what property users care about, and I was
> hoping it would be that with this option turned on you can always tell
> all symbols apart from all other symbols.

 sym-nodups ?

 sym-differentiate ?

I don't think sym-unique is worse than sym-unambigous

We could always put this question out to social media.

-- Steve



[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux