Fix misspellings of "whether" in comments.
"Whether" is misspelled in various comments across the tree; this fixes them. No code changes. Signed-off-by: Adam Buchbinder <adam.buchbinder@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
此提交包含在:
@@ -148,7 +148,7 @@ static int spider_set_irq_type(struct irq_data *d, unsigned int type)
|
||||
|
||||
/* Configure the source. One gross hack that was there before and
|
||||
* that I've kept around is the priority to the BE which I set to
|
||||
* be the same as the interrupt source number. I don't know wether
|
||||
* be the same as the interrupt source number. I don't know whether
|
||||
* that's supposed to make any kind of sense however, we'll have to
|
||||
* decide that, but for now, I'm not changing the behaviour.
|
||||
*/
|
||||
@@ -220,7 +220,7 @@ static void spider_irq_cascade(unsigned int irq, struct irq_desc *desc)
|
||||
/* For hooking up the cascace we have a problem. Our device-tree is
|
||||
* crap and we don't know on which BE iic interrupt we are hooked on at
|
||||
* least not the "standard" way. We can reconstitute it based on two
|
||||
* informations though: which BE node we are connected to and wether
|
||||
* informations though: which BE node we are connected to and whether
|
||||
* we are connected to IOIF0 or IOIF1. Right now, we really only care
|
||||
* about the IBM cell blade and we know that its firmware gives us an
|
||||
* interrupt-map property which is pretty strange.
|
||||
@@ -232,7 +232,7 @@ static unsigned int __init spider_find_cascade_and_node(struct spider_pic *pic)
|
||||
int imaplen, intsize, unit;
|
||||
struct device_node *iic;
|
||||
|
||||
/* First, we check wether we have a real "interrupts" in the device
|
||||
/* First, we check whether we have a real "interrupts" in the device
|
||||
* tree in case the device-tree is ever fixed
|
||||
*/
|
||||
struct of_irq oirq;
|
||||
|
新增問題並參考
封鎖使用者