On Tue, Mar 14, 2023 at 09:04:53AM -0700, Alison Schofield wrote: > On Tue, Mar 14, 2023 at 01:07:59AM +0100, Philipp Hortmann wrote: > > On 3/13/23 21:43, Kloudifold wrote: > > > The sm750 driver had some functions named in CamelCase, > > > which violates the kernel's naming convention. > > > In this patch, I rename these functions to snake case, > > > which is the expected style. > > > > Hi, > > please make the Subject more unique. Many patches could have this name. > > Look for examples in: > > https://lore.kernel.org/linux-staging/ > > > > Please use your full name consisting of a given name and a family name in > > front of your email. Or is this not possible and "Kloudifold" is both? > > Kloudifold, > > It'll probably take a bit for the change, allowing pseudonyms, to become > common knowledge. When the question comes up, you can just point to the > latest update to Documentation/process/submitting-patches.rst as I've > done below. > > Phillip, > I commented similar to you, and then discovered this: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d4563201f33a022fc0353033d9dfeb1606a88330 > > Pseudonyms now allowed. "Known pseudonyms" are now allowed. So that means that somehow I need to "know" this is actually a pseudonym and that it is unique and so on. As you are dealing with outreachy already, odds are you have to use a non-pseudonym for them in order to track patches and payments and the like, so please use the identifier you use with outreachy. thanks, greg k-h
