Searched refs:expecting (Results 1 – 16 of 16) sorted by relevance
49 name "a/x" should be notified to a program expecting notifications on50 directory "a", but will not be notified to one expecting notifications on
181 unsigned int expecting; member
237 expect->expectant->expecting--; in __unexpect_related()330 if (ct->expecting) in destroy_conntrack()746 expected->expectant->expecting--; in init_conntrack()993 related_to->expecting >= related_to->helper->max_expected) { in ip_conntrack_expect_related()1069 related_to->expecting++; in ip_conntrack_expect_related()
142 consistent with what archs are expecting.
763 was not expecting this to happen. A device may behave so to
80 caused grief for many people who inadvertently purchased a system expecting
929 ; Indicate that we should be expecting a disconnect
1106 ; Indicate that we should be expecting a disconnect
1352 was not expecting this to happen. A device may behave so to
212 For drivers expecting variable length packets i.e. USB client, it is
265 it was expecting one (on any feasible IRQ). If <n> is negative,267 it was expecting to receive just one from the CDROM drive.
245 * We aren't expecting a272 * We aren't expecting a
715 * when we were expecting
163 * We aren't expecting a bus free, so interrupt
37 due to Norton Utilities not expecting the root node to have moved.
6 # welcome (if they are accurate), we're eagerly expecting new entries,