spi: oc-tiny: Remove unused of_gpio.h
PATCH 1/1 spi: oc-tiny: Remove unused of_gpio.h
of_gpio.h is deprecated and subject to remove.
The driver doesn't use it, simply remove the unused header.
--- drivers/spi/spi-oc-tiny.c | 2 -- 1 file changed, 2 deletions(-)
drivers/spi/spi-oc-tiny.c +0 -2
@@ -184,8 +184,6 @@ static irqreturn_t tiny_spi_irq(int irq, void *dev) }#ifdef CONFIG_OF -#include <linux/of_gpio.h> -static int tiny_spi_of_probe (struct platform_device *pdev) {struct tiny_spi *hw =platform_get_drvdata (pdev);
Signature · 1 line
2.43.0.rc1.1.gbec44491f096
Quoted 2 lines · Andy Shevchenko
of_gpio.his deprecated and subject to remove.
The driver doesn't use it, simply remove the unused header.
Hmm... did it fall through cracks or anything should I do?
Signature · 2 lines
With Best Regards, Andy Shevchenko
Mark Brown
maintainerQuoted 5 lines · Andy Shevchenko
Quoted 2 lines · Andy Shevchenko
of_gpio.his deprecated and subject to remove.
The driver doesn't use it, simply remove the unused header.Hmm... did it fall through cracks or anything should I do?
Please don't send content free pings and please allow a reasonable time for review. People get busy, go on holiday, attend conferences and so on so unless there is some reason for urgency (like critical bug fixes) please allow at least a couple of weeks for review. If there have been review comments then people may be waiting for those to be addressed.
Sending content free pings adds to the mail volume (if they are seen at all) which is often the problem and since they can't be reviewed directly if something has gone wrong you'll have to resend the patches anyway, so sending again is generally a better approach though there are some other maintainers who like them - if in doubt look at how patches for the subsystem are normally handled.
Quoted 13 lines · Mark Brown
Quoted 5 lines · Andy Shevchenko
Quoted 2 lines · Andy Shevchenko
of_gpio.his deprecated and subject to remove.
The driver doesn't use it, simply remove the unused header.Hmm... did it fall through cracks or anything should I do?
Please don't send content free pings and please allow a reasonable time for review. People get busy, go on holiday, attend conferences and so on so unless there is some reason for urgency (like critical bug fixes) please allow at least a couple of weeks for review. If there have been review comments then people may be waiting for those to be addressed.
Quoted 6 lines
Sending content free pings adds to the mail volume (if they are seen at all) which is often the problem and since they can't be reviewed directly if something has gone wrong you'll have to resend the patches anyway, so sending again is generally a better approach though there are some other maintainers who like them - if in doubt look at how patches for the subsystem are normally handled.
Right, but it looks like this is quite simple one that simply got unnoticed or so...
Signature · 2 lines
With Best Regards, Andy Shevchenko