search for: patch5

...t; Cheers, > Rafael > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121008/0599d7ba/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: relative_ids.patch5 Type: application/octet-stream Size: 38577 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121008/0599d7ba/attachment.obj>

> Thanks for taking a look! I wasn't sure of better way to toggle this > behavior at the module level vs the function level. The options I toyed > with were: > > (a) bump MODULE_CODE_VERSION from 0 to 1 > (b) add a new optional module code to identify the change > (c) stick with the approach in the first patch, which used a new function > block ID value, then

add a hypercall number for virtual device in unmodified guest There are 6 patches for para-driver support in vmx guest. This is the first one. Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com> Signed-off-by: Arun Sharma <arun.sharma@intel.com> diff -r 287d36b46fa3 xen/arch/x86/x86_32/entry.S --- a/xen/arch/x86/x86_32/entry.S Tue Aug 30 20:36:49 2005 +++

On Sun, Sep 30, 2012 at 9:09 AM, Chris Lattner <clattner at apple.com> wrote: > > On Sep 25, 2012, at 5:08 PM, Jan Voung <jvoung at chromium.org> wrote: > > Hi all, > > I've been looking into how to make llvm bitcode files smaller. There is > one simple change that appears to shrink linked bitcode files by about 15%. > See this spreadsheet for some rough

...67 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20081215/decaba25/attachment-0013.obj> -------------- next part -------------- Patch #5. Required by Apple's lawyers. -------------- next part -------------- A non-text attachment was scrubbed... Name: patch5 Type: application/octet-stream Size: 419 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20081215/decaba25/attachment-0014.obj> -------------- next part --------------

hi guys can anyone give me info how to patch postfix with VDA? im using centos 4 with postfix-2.1.5-4.2. I downloaded the postfix-2.1.5-4.2.RHEL4.src.rpm to recompile it with VDA. i also downloaded the patch for postfix to support VDA. i added a line in postfix.spec Patch8: postfix-2.1.5-trash.patch for the VDA. but when i compiled it it seems that it doesn't compile with the given patch

Hi, Patch1 add a helper to get virtio_device's status which will be used later. Patch2~4: check virtio_device's status is RTIO_CONFIG_S_ACKNOWLEDGE or not, if so use put_device otherwise use kfree. Patch5: add comments for virtio_register_device help caller do a proper cleanup if got failure. weiping zhang (5): virtio: add helper virtio_get_status virtio_pci: don't kfree device on register failure virtio_vop: don't kfree device on register failure virtio_remoteproc: don't kfree...

Hi, Patch1 add a helper to get virtio_device's status which will be used later. Patch2~4: check virtio_device's status is RTIO_CONFIG_S_ACKNOWLEDGE or not, if so use put_device otherwise use kfree. Patch5: add comments for virtio_register_device help caller do a proper cleanup if got failure. weiping zhang (5): virtio: add helper virtio_get_status virtio_pci: don't kfree device on register failure virtio_vop: don't kfree device on register failure virtio_remoteproc: don't kfree...

...V_cdb}.tar.gz Source16: http://postfix.wl0.org/ftp/postfinger/postfinger-%{V_postfinger} # Sources >= 100 are config files Source100: postfix-sasl.conf Source101: postfix-pam.conf Source102: postfix-saslauthd.conf # Obligatory Patches Patch0: postfix-2.3.3-vda.patch Patch3: postfix-files.patch Patch5: postfix-makedefs.patch # Optional patches # FIXME: There is also a 64-bit patch (not included) for 2.5.4 Patch4: http://vda.sourceforge.net/VDA/postfix-%{V_vda}-vda-ng.patch.gz # SPF patch Patch8: http://www.linuxrulz.org/nkukard/postfix/postfix-2.3/postfix-2.3.2_libspf2-1.2.x-20060819.patch P...

...}.tar.gz Source16: http://postfix.wl0.org/ftp/postfinger/postfinger-%{V_postfinger} # Sources >= 100 are config files Source100: postfix-sasl.conf Source101: postfix-pam.conf Source102: postfix-saslauthd.conf Patch0: postfix-vda-v10-2.8.4.patch # Obligatory Patches Patch3: postfix-files.patch Patch5: postfix-makedefs.patch # Optional patches # FIXME: There is also a 64-bit patch (not included) for 2.5.4 Patch4: http://vda.sourceforge.net/VDA/postfix-%{V_vda}-vda-ng.patch.gz # SPF patch Patch8: http://www.linuxrulz.org/nkukard/postfix/postfix-2.3/postfix-2.3.2_libspf2-1.2.x-20060819.patch P...

...TRL vq's. 2. num_queue_pairs instead of numtxqs. 3. Experimental support for fewer irq's in find_vqs. Rusty: ------ 4. Cleaned up some existing "while (1)". 5. rvq/svq and rx_sg/tx_sg changed to vq and sg respectively. 6. Cleaned up some "#if 1" code. Issue when using patch5: ------------------------- The new API is designed to minimize code duplication. E.g. vp_find_vqs() is implemented as: static int vp_find_vqs(...) { return vp_find_vqs_irq(vdev, nvqs, vqs, callbacks, names, NULL); } In my testing, when multiple tx/rx is used with multiple netperf sessions, all...

...TRL vq's. 2. num_queue_pairs instead of numtxqs. 3. Experimental support for fewer irq's in find_vqs. Rusty: ------ 4. Cleaned up some existing "while (1)". 5. rvq/svq and rx_sg/tx_sg changed to vq and sg respectively. 6. Cleaned up some "#if 1" code. Issue when using patch5: ------------------------- The new API is designed to minimize code duplication. E.g. vp_find_vqs() is implemented as: static int vp_find_vqs(...) { return vp_find_vqs_irq(vdev, nvqs, vqs, callbacks, names, NULL); } In my testing, when multiple tx/rx is used with multiple netperf sessions, all...