Re: [PATCH v4] modules: introduce the MODULE_SCMVERSION config

Hi Jessica, I looked into the LOCALVERSION= part more and finally figured out how that part of the script works. I wasn't familiar with how the parameter substitution worked -- ${parameter:+alt_value}. I verified that we will only get an SCM version returned when LOCALVERSION_AUTO=y and updated

Re: [PATCH v4] modules: introduce the MODULE_SCMVERSION config

+++ Will McVicker [06/01/21 10:44 -0800]: Thanks for the vacation notice Jessica! I'm just letting you know I'm back as well and am happy to respond to any concerns regarding v4 when you get all caught up. I hope you had a relaxing holiday :) Hi Will - thanks, same to you! On Fri, Dec 18,

Re: [PATCH v4] modules: introduce the MODULE_SCMVERSION config

Thanks for the vacation notice Jessica! I'm just letting you know I'm back as well and am happy to respond to any concerns regarding v4 when you get all caught up. I hope you had a relaxing holiday :) Thanks, Will On Fri, Dec 18, 2020 at 4:01 AM Jessica Yu wrote: > > +++ Will McVicker

Re: [PATCH v4] modules: introduce the MODULE_SCMVERSION config

+++ Will McVicker [16/12/20 22:08 +]: Config MODULE_SCMVERSION introduces a new module attribute -- `scmversion` -- which can be used to identify a given module's SCM version. This is very useful for developers that update their kernel independently from their kernel modules or vice-versa