summaryrefslogtreecommitdiff
path: root/trie.h
blob: c46399192032ebea0449cdba82e3b5dcc9815eb5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
#ifndef TRIE_H
#define TRIE_H

#include <netinet/in.h>

extern void trie_addr_lookup(char *buff, size_t len, int ipv4, int *fd,
			     struct sockaddr_storage *addr, size_t *alen);
extern int trie_addr_maybe_update(char *buff, size_t len, int ipv4, int fd,
				  struct sockaddr_storage *addr, size_t alen);
extern void trie_addr_remove(int fd);
extern void trie_addr_remove_addr(struct sockaddr_storage *addr, size_t alen);
extern void trie_init(void);
extern void trie_cleanup(void);

#endif /* TRIE_H */
/td>2016-09-19 09:49:27 +0100 committerThomas Gleixner <tglx@linutronix.de>2016-09-19 11:31:36 +0200 commit1984e075915cbae65336a99b1879865080d8e55e (patch) tree7821bac4d017d04a8b6563493bb767af11b22f74 parent3be7988674ab33565700a37b210f502563d932e6 (diff)
genirq: Skip chained interrupt trigger setup if type is IRQ_TYPE_NONE
There is no point in trying to configure the trigger of a chained interrupt if no trigger information has been configured. At best this is ignored, and at the worse this confuses the underlying irqchip (which is likely not to handle such a thing), and unnecessarily alarms the user. Only apply the configuration if type is not IRQ_TYPE_NONE. Fixes: 1e12c4a9393b ("genirq: Correctly configure the trigger on chained interrupts") Reported-and-tested-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com> Link: https://lkml.kernel.org/r/CAMuHMdVW1eTn20=EtYcJ8hkVwohaSuH_yQXrY2MGBEvZ8fpFOg@mail.gmail.com Link: http://lkml.kernel.org/r/1474274967-15984-1-git-send-email-marc.zyngier@arm.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat