search for: marcro

Displaying 5 results from an estimated 5 matches for "marcro".

Did you mean: macro
2023 Mar 01
5
[PATCH 0/2] drm/nouveau: avoid usage of list iterator after loop
This patch set includes two instances where the list iterator variable 'pstate' is implicitly assumed to be valid after the iterator loop. While in pratice that is most likely the case (if 'pstatei'/'args->v0.state' is <= the elements in clk->states), we should explicitly only allow 'pstate' to always point to correct 'nvkm_pstate' structs. That
2005 Jul 26
2
Stumped on vMail problem, any ideas?
...f I see: [ext-local] include => ext-local-custom exten => 200,1,Macro(exten-vm,200@default,200) exten => ${VM_PREFIX}200,1,Macro(vm,200) exten => 201,1,Macro(exten-vm,201@default,201) exten => ${VM_PREFIX}201,1,Macro(vm,201) Looking under my AAH extensions.conf I see the following marcro's: ; Ring an extension, if the extension is busy or there is no answer send it ; to voicemail ; ARGS: $VMBOX, $EXT [macro-exten-vm] exten => s,1,Setvar(FROMCONTEXT=exten-vm) exten => s,2,Macro(record-enable,${ARG2},IN) exten => s,3,Macro(dial,${RINGTIMER},${DIAL_OPTIONS},${ARG2}) exte...
2018 Jun 11
0
[PATCH v3 6/9] x86: prevent inline distortion by paravirt ops
...umber. > + * The type number, computed in PARAVIRT_PATCH, is derived from the > + * offset into the paravirt_patch_template structure, and can therefore be > + * freely converted back into a structure offset. > + */ > +.macro PARAVIRT_ALT type:req clobber:req pv_opptr:req Unlike the marcro maze you replaced, this has the CALL hardcoded in. So maybe name this PARAVIRT_CALL instead of PARAVIRT_ALT ? > +771: ANNOTATE_RETPOLINE_SAFE > + call *\pv_opptr > +772: .pushsection .parainstructions,"a" > + _ASM_ALIGN > + _ASM_PTR 771b > + .byte \type > + .byte 772...
2023 Mar 07
0
[PATCH 1/2] drm/nouveau/device: avoid usage of list iterator after loop
...llows > adding a BUG_ON in case the code works incorrectly, exposing currently > undetectable potential bugs. > > Additionally, Linus proposed to avoid any use of the list iterator > variable after the loop, in the attempt to move the list iterator > variable declaration into the marcro to avoid any potential misuse after > the loop [1]. > > Link: https://lore.kernel.org/all/CAHk-=wgRr_D8CB-D9Kg-c=EHreAsk5SqXPwr9Y7k9sA6cWXJ6w at mail.gmail.com/ [1] > Signed-off-by: Jakob Koschel <jkl820.git at gmail.com> > --- > drivers/gpu/drm/nouveau/nvkm/engine/device/...
2008 Aug 29
0
Asterisk cdr_mysql inexact values
...,%Y%m%d-%H%M%S)}) exten => _00[123459]XXXXXXXX!,2,GotoIf($[${DB(internet/disponible)}=1]?3:7) exten => _00[123459]XXXXXXXX!,3,GotoIf($[${DB(moyende/telecom)}=0]?4:6) exten => _00[123459]XXXXXXXX!,4,Macro(phonesystems,${EXTEN}) exten => _00[123459]XXXXXXXX!,5,Hangup() ;this hangup is for marcro returning exten => _00[123459]XXXXXXXX!,6,GotoIf($[${DB(moyende/telecom)}=1]?7:8) ;case 8 should never happen, just in case. exten => _00[123459]XXXXXXXX!,7,Dial(mISDN/g:intern-out/${EXTEN:1}) exten => _00[123459]XXXXXXXX!,8,Dial(mISDN/g:intern-out/${EXTEN:1}) Thank you. -------------- ne...