@@ -2102,8 +2102,6 @@ static void __init prom_init_stdout(void)stdout_node=call_prom("instance-to-package",1,1,prom.stdout);if(stdout_node!=PROM_ERROR){val=cpu_to_be32(stdout_node);-prom_setprop(prom.chosen,"/chosen","linux,stdout-package",-&val,sizeof(val));/* If it's a display, note it */memset(type,0,sizeof(type));
That is going to confuse some scripts that are expecting that to be a
"Fixes: <some commit>" tag :)
The proper tag to use there would be "Link:".
But, I'd prefer we didn't add github issue links to the history, as I'm
not sure they won't bit-rot eventually. Not because I'm a anti-Microsoft
conspiracy person but just because it's a repo I set up and manage and
there's no long term plan for it necessarily.
Including the link here would be ideal, as it means it doesn't end up in
the commit history, but it does end up in the mail archive. So if we
ever really need to find it, it should be there.
cheers
@@ -2102,8 +2102,6 @@ static void __init prom_init_stdout(void)stdout_node=call_prom("instance-to-package",1,1,prom.stdout);if(stdout_node!=PROM_ERROR){val=cpu_to_be32(stdout_node);-prom_setprop(prom.chosen,"/chosen","linux,stdout-package",-&val,sizeof(val));/* If it's a display, note it */memset(type,0,sizeof(type));
That is going to confuse some scripts that are expecting that to be a
"Fixes: <some commit>" tag :)
The proper tag to use there would be "Link:".
But, I'd prefer we didn't add github issue links to the history, as I'm
not sure they won't bit-rot eventually. Not because I'm a anti-Microsoft
conspiracy person but just because it's a repo I set up and manage and
there's no long term plan for it necessarily.
Including the link here would be ideal, as it means it doesn't end up in
the commit history, but it does end up in the mail archive. So if we
ever really need to find it, it should be there.
cheers
That is going to confuse some scripts that are expecting that to be a
"Fixes: <some commit>" tag :)
The proper tag to use there would be "Link:".
But, I'd prefer we didn't add github issue links to the history, as I'm
not sure they won't bit-rot eventually. Not because I'm a anti-Microsoft
conspiracy person but just because it's a repo I set up and manage and
there's no long term plan for it necessarily.
Including the link here would be ideal, as it means it doesn't end up in
the commit history, but it does end up in the mail archive. So if we
ever really need to find it, it should be there.
cheers
Thanks.
I had actually already applied the first version, but I didn't say that
in my email did I :}
So I've rebased and applied your v2, thanks.
cheers