search for: reindenting

...e: > > > > This is a known problem, I just haven't had time to do anything about > it yet (had my final exam today). > > >The patch is a small change but looks longer because I indented the > >code. > > Well... don't do that, then. Patches that do mass reindenting will > always be rejected, unless there's a REALLY good reason to do so > (you not liking my indentation style is a very poor reason). I didn't do a massive reindenting. I reindented just that small part of the code. I thought it was a mess. Was it supposed to be like that? > Mi...

Signed-off-by: Adalbert Laz?r <alazar at bitdefender.com> --- arch/x86/kvm/mmu/mmu.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c index 97766f34910d..f3ba4d0452c9 100644 --- a/arch/x86/kvm/mmu/mmu.c +++ b/arch/x86/kvm/mmu/mmu.c @@ -2573,6 +2573,7 @@ static struct kvm_mmu_page *kvm_mmu_get_page(struct kvm_vcpu *vcpu,

The icecast2 code uses recv(2) to read data from a source and tests its returning value to see if something went wrong. The current code groups together two checks of the return value: - Returning 0 - Returning -1 and a non-recoverable error and gives the same error message for both. Since returning 0 means the connection has ended the following debug message showed up in error.log: DBUG

Debian bug 812166[0] reported this build failure due to Wmisleading-indentation with gcc-6: non-fatal.c: In function 'init_nonfatal_mce_checker': non-fatal.c:103:2: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation] switch (c->x86_vendor) { ^~~~~~ non-fatal.c:97:5: note: ...this 'if' clause, but it is not if (

...sier to use >> an attribute((cleanup)) handler to deal with the unlocking. See these >> links for how we do it in libguestfs: > > Oh cool! Yes, that looks nicer. Although the diffstat for doing so is > larger, because it requires adding to new sub-function {} scopes and > reindenting (we have two different locks in play here). > Interestingly, it doesn't compile if you lack attribute((cleanup)). Libguestfs has: common/utils/cleanups.h:/* XXX no safe equivalent to CLEANUP_GL_RECURSIVE_LOCK_UNLOCK */ and will fail to compile if the compiler lacks the attribute - arguab...

(emacs newb here) After having made some changes in an \items paragraph of \arguments the lines are no longer nicely wrapped. I was looking for a command to reindent/rewrap/reformat the whole \items paragraph but couldn't find anything. The only way, I found, was to go to the end of the first line, do 'c-j' (or RET) which wraps *this* line nicely, but now there is a hard line-break

On Tue, Apr 05, 2016 at 01:47:29PM +0200, Cédric Bosdonnat wrote: > The output of the first boot scripts is available in the guest as > -F<C:\Program Files\Red Hat\Firstboot\log.txt>. > +F<C:\Program Files\Guestfs\Firstboot\log.txt>. Changing this path is fine, but let's split it into a separate patch. > + let services = ["rhsrvany.exe";

On Thu, Nov 16, 2017 at 09:26:54PM -0600, Eric Blake wrote: > In preparation for parallel processing, we need to be sure that > two threads belonging to the same connection cannot interleave > their I/O except at message boundaries. Add a mutex around > all reads and writes that must occur as a group (for now, there > is no contention for either mutex). > > Signed-off-by:

On 22/01/16 14:38, Ian Campbell wrote: > Debian bug 812166[0] reported this build failure due to > Wmisleading-indentation with gcc-6: > > non-fatal.c: In function 'init_nonfatal_mce_checker': > non-fatal.c:103:2: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation] > switch (c->x86_vendor) { > ^~~~~~ > >

...is patch, but it might be easier to use > an attribute((cleanup)) handler to deal with the unlocking. See these > links for how we do it in libguestfs: Oh cool! Yes, that looks nicer. Although the diffstat for doing so is larger, because it requires adding to new sub-function {} scopes and reindenting (we have two different locks in play here). -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org

...; an attribute((cleanup)) handler to deal with the unlocking. See these >>> links for how we do it in libguestfs: >> >> Oh cool! Yes, that looks nicer. Although the diffstat for doing so is >> larger, because it requires adding to new sub-function {} scopes and >> reindenting (we have two different locks in play here). >> > > Interestingly, it doesn't compile if you lack attribute((cleanup)). > Libguestfs has: > > common/utils/cleanups.h:/* XXX no safe equivalent to > CLEANUP_GL_RECURSIVE_LOCK_UNLOCK */ > > and will fail to compile i...

Do CentOS 5.4 users still have to use the RedHat preliminary kernels (http://people.redhat.com/jlayton/) for getting a NFSv4 safe kernel or have the patches been incorporated into CentosPlus kernels? Or is kernel-2.6.18-164.3.1.el5 somewhere in the queue? Thanks in advance! GS -- Gerhard Schneider Institute of Lightweight Design and e-Mail: gs at ilsb.tuwien.ac.at Structural

Reindent with -bad -bap -c0 -cd0 -cp0 -ncdb -ci4 -cli0 -ncs -d0 -di4 -i4 -ip4 -l80 -npcs -psl -sob -ss -ce -sc -br -cdw -lp -cbi0. Bug #6286: Fix build on Cygwin. (Yaakov Selkowitz) Bug #5628 <https://bugs.freedesktop.org/show_bug.cgi?id=5628> Shadow pages not created correctly when MANDIR & MANSUFFIX don't match. CVS tag: libXi-1_0_1

https://bugzilla.netfilter.org/show_bug.cgi?id=856 Summary: configure is checking kernel stuff even when the kmod build was disabled Product: ipset Version: unspecified Platform: x86_64 OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: default AssignedTo:

Petr Pikal said: > I am not really a R specialist but for this task I use function: and he pasted his code into the email. I reindented the code, and wrote a fragment to experiment with it. Here it is: --------------------------------------------------------------------------- plot.yy <- function(x, yright, yleft, yleftlim=NULL, yrightlim = NULL,

A variety of bugfixes across the board, primarily in Xwayland and PRIME. This release also includes GLX vendor selection support. Thanks to all who contributed with testing and fixes! Aaron Plattner (3): GLX: Set GlxServerExports::{major,minor}Version xfree86: Call ScreenInit for protocol screens before GPU screens os: Don't crash in AttendClient if the client is gone Adam

I had originally thought that I'd do a complete audit of the Dovecot's sources this weekend, but looks like I didn't. Hopefully I've been writing good enough code that the "1000 EUR for security hole" offer lasts for a long time. :) This release should fix the SSL parameter regeneration problem. There were two changes that were needed to fix it, but I had forgotten the

I'm pleased to announce the 7.8.0 release of xf86-video-ati, the Xorg driver for ATI/AMD Radeon GPUs supported by the radeon kernel driver. This release supports xserver versions 1.10-1.19. Highlights: * Significant 2D compositing performance increase, in particular with glamor enabled. * Option "TearFree" can now prevent tearing in all possible display configurations (with

https://bugzilla.mindrot.org/show_bug.cgi?id=2361 Bug ID: 2361 Summary: seccomp filter (not only) for aarch64 Product: Portable OpenSSH Version: 6.7p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: sshd Assignee: unassigned-bugs at

Hi, I was building LLVM with gcc 6.1.1 recently and it was spitting out some warnings relating to misleading indention that caught my eye. This wasn't a fresh build so I may have missed some. I've CC'ed the authors of the potentially misleading lines so they can decide what do about the warnings (if anything). I'm wondering if clang-format is making some inappropriate choices