patacongo commented on issue #353: multiple definition of `up_mdelay'
URL: https://github.com/apache/incubator-nuttx/issues/353#issuecomment-590079793
 
 
   > Not a whole architecture, different chipset in the same architecture can 
select the different approach because each chipset has own Make.defs and can 
include/exclude up_delay.c as needed, but the same chipset must share the same 
decision.
   
   Isn't that just an abritrary limitation?  Why should implementation on any 
architecture have this option?  Why limit it to just certain, pre-determined 
architectures?
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to