search for: _empty

...s. Being able to conditionally add the cleanup function (where we don't want it on non-pointer vectors) makes sense, but removing the iterator function at the same time is a step too far. > > Remove the generic "name##_iter" function definition, and introduce > "name##_empty", which performs both steps at the same time. Convert the > call sites. (Note that the converted code performs more cleanup steps in > some cases than strictly necessary, but the extra work is harmless, and > arguably beneficial for clarity / consistency.) Agreed that the extra clean...

Hello, A GUI program uses rsync for network transfers. It is able to load filters from a file by putting a dot and underscore before it. Example:mkdir 1 2; touch 1/a .empty; rsync -f ._empty 1/ 2/ Is the dot underscore specific to rsync or is it a general bash (or similar?) feature to load arguments from a file? And is it documented anywhere for rsync? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments...

..._TYPE() macro to take a third argument containing the > >>> function name to call on cleanup paths, with the ability to easily > >>> write/reuse a no-op function for vectors that don't need to call > >>> free(), where we can then unconditionally declare name##_empty() that > >>> will work with all vector types? That is, should we consider instead > >>> doing something like: > >>> > >>> DEFINE_VECTOR_TYPE (string_vector, char *, free); > >>> > >>> DEFINE_VECTOR_TYPE (int_vector, int, noop)...

...+ return NULL; \ +} \ + \ +static void RBPREFIX ## _remove(RBCTYPE *_container, RBNTYPE *_node) \ +{ \ + rb_erase(&_node->_rb_node, &_container->_rb_root); \ + RB_CLEAR_NODE(&_node->_rb_node); \ +} \ + \ +static bool RBPREFIX ## _empty(const RBCTYPE *_container) \ +{ \ + return RB_EMPTY_ROOT(&_container->_rb_root); \ +} \ + +#ifdef CONFIG_REMOTE_MAPPING +extern int mm_remote_map(struct mm_struct *req_mm, + unsigned long req_hva, unsigned long map_hva); +extern int mm_remote_unmap(unsigned long map_hva...

The KVM introspection subsystem provides a facility for applications running on the host or in a separate VM, to control the execution of other VM-s (pause, resume, shutdown), query the state of the vCPUs (GPRs, MSRs etc.), alter the page access bits in the shadow page tables (only for the hardware backed ones, eg. Intel's EPT) and receive notifications when events of interest have taken place

The KVM introspection subsystem provides a facility for applications running on the host or in a separate VM, to control the execution of other VM-s (pause, resume, shutdown), query the state of the vCPUs (GPRs, MSRs etc.), alter the page access bits in the shadow page tables (only for the hardware backed ones, eg. Intel's EPT) and receive notifications when events of interest have taken place