search for: 713,11

Displaying 7 results from an estimated 7 matches for "713,11".

Did you mean: 213,11
2004 Jun 20
2
[PATCH] fixup journal-related ifdef mess
...dle to disk in abort case. */ handle->k_handle->h_sync = 1; - retval = ocfs_journal_stop(handle->k_handle); + retval = journal_stop(handle->k_handle); if (retval < 0) { LOG_ERROR_STR("Could not commit aborted transaction!"); LOG_ERROR_STATUS(retval); @@ -705,19 +713,11 @@ switch (type) { case OCFS_JOURNAL_ACCESS_CREATE: case OCFS_JOURNAL_ACCESS_WRITE: -#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0) status = journal_get_write_access(handle->k_handle, bh, NULL); -#else - status = journal_get_write_access(handle->k_handle, bh); -#endif brea...
2006 Sep 01
3
[LLVMdev] gfortran: patch, question
...n routines are called. I'm looking into the errors, and I'll update the list on any progress. Index: gcc/fortran/f95-lang.c =================================================================== --- gcc/fortran/f95-lang.c (revision 160) +++ gcc/fortran/f95-lang.c (working copy) @@ -713,7 +713,11 @@ TREE_PUBLIC (decl) = 1; if (library_name) SET_DECL_ASSEMBLER_NAME (decl, get_identifier (library_name)); +#ifndef ENABLE_LLVM make_decl_rtl (decl); +#else + make_decl_llvm (decl); +#endif pushdecl (decl); DECL_BUILT_IN_CLASS (decl) = class; DECL_FUNCTION_CODE (d...
2006 Sep 01
0
[LLVMdev] gfortran: patch, question
On Fri, 1 Sep 2006, Michael McCracken wrote: > Hi, I have a first quick patch and a question. The patch links f951 > with g++ when LLVM is enabled. It's at the end of this email. Thanks, applied! > I wanted to know if I should submit patches with comments around them > like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to > the tree. I'd like to
2006 Sep 01
2
[LLVMdev] gfortran: patch, question
Hi, I have a first quick patch and a question. The patch links f951 with g++ when LLVM is enabled. It's at the end of this email. I wanted to know if I should submit patches with comments around them like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to the tree. I'd like to make it as easy as possible to apply these, so let me know any rules I should be following.
2014 May 20
14
Re: [PATCH] daemon: scrub-file: resolve the path before calling scrub (RHBZ#1099490).
On Tuesday 20 May 2014 15:56:16 Richard W.M. Jones wrote: > On Tue, May 20, 2014 at 03:33:31PM +0200, Pino Toscano wrote: > > Resolve the given path within the chroot, so scrub can be invoked > > outside the chroot on an already-resolved path. > > Given that realpath is used, its availability is checked manually, > > since scrub-file already depends on the
2023 Feb 24
1
[PATCH 1/1] Add support for ZSTD compression
...;state->compression_out_stream); switch (deflateInit(&ssh->state->compression_out_stream, level)) { case Z_OK: - ssh->state->compression_out_started = 1; + ssh->state->compression_out_started = COMP_ZLIB; break; case Z_MEM_ERROR: return SSH_ERR_ALLOC_FAIL; @@ -713,11 +744,11 @@ start_compression_out(struct ssh *ssh, int level) static int start_compression_in(struct ssh *ssh) { - if (ssh->state->compression_in_started == 1) + if (ssh->state->compression_in_started == COMP_ZLIB) inflateEnd(&ssh->state->compression_in_stream); swit...
2023 Feb 24
1
[PATCH 0/1] ZSTD compression support for OpenSSH
I added ZSTD support to OpenSSH roughly three years ago and I've been playing with it ever since. The nice part is that ZSTD achieves reasonable compression (like zlib) but consumes little CPU so it is unlikely that compression becomes the bottle neck of a transfer. The compression overhead (CPU) is negligible even when uncompressed data is tunneled over the SSH connection (SOCKS proxy, port