-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some details noted #16
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: <Michael Heltne [email protected]>
// Generated with linux-mdss-dsi-panel-driver-generator from vendor device tree: | ||
// Copyright (c) 2013, The Linux Foundation. All rights reserved. (FIXME) | ||
/* | ||
* SPDX-License-Identifier: GPL-2.0-only |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The SPDX-License-Identifier should be a //
comment, see https://www.kernel.org/doc/html/latest/process/license-rules.html#license-identifier-syntax
For the other Copyright text it varies in the kernel tree. Most are using /* ... */
, but there are also some which are not, see e.g. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/panel/panel-samsung-s6e88a0-ams452ef01.c
So I think it might be fine to keep this as-is. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes, that SPDX as // struck me around the time i hit the pillow. Well, I'm two phased there, perhaps it's a good idea to encourage people to get to know the script a little and edit as needed as nothing can be guaranteed as perfect, but on the other hand, just grabbing it, generating a panel file and then just editing the output a bit would be optimal as well.
Cheers and thanks for all the panel drivers!
5d3795c
to
673e435
Compare
but the original generated example i cant find??? Signed-off-by: <Michael Heltne [email protected]>
I edited the readme a bit, i'm not sure i'm happy with the last one just yet, and i'll be staring (at goats) until i understand for a while longer. Got any suggestions? I look at it and want to shorten down so it fits with the rest, but that's OCD. |
So I thought it might be nice if the headers comply with coding conduct for the kernel?