search for: unintentional

the clang 3.5 loop optimizer seems to jump in unintentional for simple loops the very simple example ---- const int SIZE = 3; int the_func(int* p_array) { int dummy = 0; #if defined(ITER) for(int* p = &p_array[0]; p < &p_array[SIZE]; ++p) dummy += *p; #else for(int i = 0; i < SIZE; ++i) dummy += p_array[i]; #endif return dum...

This is the only use of kerneldoc in the sourcefile and no descriptions are provided. Fixes the following W=1 kernel build warning(s): drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'vscsi' not described in 'virtscsi_complete_cmd' drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'buf' not described in

On Mon, Jul 13, 2020 at 08:59:49AM +0100, Lee Jones wrote: > This is the only use of kerneldoc in the sourcefile and no > descriptions are provided. > > Fixes the following W=1 kernel build warning(s): > > drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'vscsi' not described in 'virtscsi_complete_cmd' > drivers/scsi/virtio_scsi.c:109:

A couple of days ago I posted some elisp code that asks the user for confirmation before deleting a process buffer, e.g. the *R* buffer. However, this code was only evaluated if a buffer was killed by means of [C-x k]. The following code does not need to be bound to a particular key, it's internally called by kill-buffer. (Also works if buffer is deleted in other ways, e.g., [C-x C-c].)

This is the only use of kerneldoc in the sourcefile and no descriptions are provided. Fixes the following W=1 kernel build warning(s): drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'vscsi' not described in 'virtscsi_complete_cmd' drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'buf' not described in

This is the only use of kerneldoc in the sourcefile and no descriptions are provided. Fixes the following W=1 kernel build warning(s): drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'vscsi' not described in 'virtscsi_complete_cmd' drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'buf' not described in

Noticed a problem for a while - tests/testit.Rd, tests/ver20.Rd are removed on "make clean" unintentionally. This seems to come from a change in tests/Makefile.in, which adds the line: - at rm -f *.tar.gz *.Rd back in May 2012. ----------- commit c4d70254e7b7f9d7ed17faecfb3097195d852ddc Author: ripley <ripley at 00db46b3-68df-0310-9c12-caf00c1e9a41> Date: Sun May 27 09:04:41 2012 +0000...

...uld not find any documentation about what the "policy" for C++ is. The check-in for 94686 seems to suggest that the C bindings are somewhat preserved, but doesn't it make sense to provide some guarantees regarding the most frequently used C++ code? Also note that the documentation is unintentionally misleading. It's very confusing for http://llvm.org/docs/tutorial/LangImpl4.html to show "Last modified: $Date: 2007-10-17 11:05:13 -0700 (Wed, 17 Oct 2007) $" at the bottom, as if nothing had changed since then, when the code it displays is actually less than a week old... I guess...

commit d85b758f72b0 "virtio_net: fix support for small rings" was supposed to increase the buffer size for small rings but had an unintentional side effect of decreasing it for large rings. This seems to break some setups - it's not yet clear why, but increasing buffer size back to what it was before helps. Fixes: d85b758f72b0 "virtio_net: fix support for small rings" Reported-by: Mikulas Patocka <mpatocka at redhat.com&g...

commit d85b758f72b0 "virtio_net: fix support for small rings" was supposed to increase the buffer size for small rings but had an unintentional side effect of decreasing it for large rings. This seems to break some setups - it's not yet clear why, but increasing buffer size back to what it was before helps. Fixes: d85b758f72b0 "virtio_net: fix support for small rings" Reported-by: Mikulas Patocka <mpatocka at redhat.com&g...

...approach. If the code is not syntactically valid, why would you expect the block comment to be syntactically valid? The proposal at the start of this thread was that #{ would open the block and would be matched by }# to close the block. What if the closing sequence occurred within the block unintentionally? Then the poor feeble programmer would be even more confused. I like the current rule: any line starting with # is a comment. (Actually the rule is a bit more subtle than that, but it's close.) If I want to comment out a block, I can spend a long time typing # at the start of every line...

...xpect a possibility > of a difference. > > > Are there any differences in their behaviors when booting with > > different Syslinux variants (e.g ISOLINUX vs. SYSLINUX vs. > > PXELINUX)? > > There shouldn't be. However, I could see EFI architecture having an > unintentional difference. > Is there some specific reason for such suspicion? Do you already have such potential unintentional difference in mind? Something specific? > > To be clear, I am asking about what (in theory) *should* be > > happening, (which might or might not be the same as to w...

Hi, all, Does R have a "const object" concept like which is in C++ language? I want to set some data frames as constant to avoid being modified unintentionally. Thanks! xiagao1982 2011-03-15 [[alternative HTML version deleted]]

...have a different CLI parser so I'd expect a possibility of a difference. > Are there any differences in their behaviors when booting with > different Syslinux variants (e.g ISOLINUX vs. SYSLINUX vs. > PXELINUX)? There shouldn't be. However, I could see EFI architecture having an unintentional difference. > To be clear, I am asking about what (in theory) *should* be > happening, (which might or might not be the same as to what actually > happens). -- -Gene

I tried building the latest master from git on debian wheezy. It seems to require libncurses-dev. I thought to add it into the wiki as a required package to install, but it seems one needs to ask for a login to the wiki. No prob ;) Could someone add it to the wiki? Or is this an unintentional dependency that will be removed? -- Michael De Groote ICT-coordinator Sint-Pietersschool Korbeek-Lo ICT-support Sancta Maria Basisschool Leuven

I wonder if the 'sep' argument in reshape() is being ignored unintentionally: ## From example(reshape) df <- data.frame(id=rep(1:4,rep(2,4)), visit=I(rep(c("Before","After"),4)), x=rnorm(4), y=runif(4)) reshape(df, timevar="visit", idvar="id", direction="wide", sep = "_")...

...". ("Release" for the Release configuration) However, for the two build configurations Release_SSE and Release_SSE2, Output Directory is "$(ConfigurationName)" and Intermediate Directory is also "$ConfigurationName)". How come this is inconsistent? If this is unintentional, which one should we use? I'll be happy to supply a patch to fix this up.

...56 AM, Michael S. Tsirkin wrote: > > >commit d85b758f72b0 "virtio_net: fix support for small rings" > > Commit d85b758f72b0 ("virtio_net: fix support for small rings") > > >was supposed to increase the buffer size for small rings > >but had an unintentional side effect of decreasing > >it for large rings. This seems to break some setups - > >it's not yet clear why, but increasing buffer size > >back to what it was before helps. > > > >Fixes: d85b758f72b0 "virtio_net: fix support for small rings" > > F...

...56 AM, Michael S. Tsirkin wrote: > > >commit d85b758f72b0 "virtio_net: fix support for small rings" > > Commit d85b758f72b0 ("virtio_net: fix support for small rings") > > >was supposed to increase the buffer size for small rings > >but had an unintentional side effect of decreasing > >it for large rings. This seems to break some setups - > >it's not yet clear why, but increasing buffer size > >back to what it was before helps. > > > >Fixes: d85b758f72b0 "virtio_net: fix support for small rings" > > F...

Hello Syslinux Team, What actions are _supposed_ to be triggered by each of: [Ctrl-J] [Ctrl-M] in the Syslinux command line in version 6.03-pre20? Are there any differences between CLI and [vesa]menu.c32 regarding these keystroke combinations? Are there any differences in their behaviors when booting with different Syslinux variants (e.g ISOLINUX vs. SYSLINUX vs. PXELINUX)? To be