search for: unecessari

Displaying 20 results from an estimated 81 matches for "unecessari".

Did you mean: unecessary
2013 May 20
2
[PATCH] Remove unecessary ERROR when removing non-empty directory
While removing a non-empty directory, the kernel dumps a message: (rmdir,21743,1):ocfs2_unlink:953 ERROR: status = -39 Suppress the error message from being printed in the dmesg so users don't panic. Signed-off-by: Goldwyn Rodrigues <rgoldwyn at suse.com> --- diff --git a/fs/ocfs2/namei.c b/fs/ocfs2/namei.c index 04ee1b5..33c7b91 100644 --- a/fs/ocfs2/namei.c +++ b/fs/ocfs2/namei.c @@
2018 Apr 27
0
[PATCH 11/17] drm/nouveau: Remove unecessary dma_fence_ops
dma_fence_default_wait is the default now. Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: nouveau at lists.freedesktop.org --- drivers/gpu/drm/nouveau/nouveau_fence.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 503fa94dc06d..444bbde65344
2018 May 03
0
[PATCH 10/15] drm/nouveau: Remove unecessary dma_fence_ops
dma_fence_default_wait is the default now. Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: nouveau at lists.freedesktop.org --- drivers/gpu/drm/nouveau/nouveau_fence.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 503fa94dc06d..444bbde65344
2018 Jul 04
0
[PATCH 3/5] drm/nouveau: Remove unecessary dma_fence_ops
dma_fence_default_wait is the default now. Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: nouveau at lists.freedesktop.org --- drivers/gpu/drm/nouveau/nouveau_fence.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 412d49bc6e56..99be61ddeb75
2018 May 02
0
[PATCH] drm/qxl: Remove unecessary dma_fence_ops
The trivial enable_signaling implementation matches the default code. v2: Fix up commit message to match patch better (Eric). Cc: Eric Anholt <eric at anholt.net> Reviewed-by: Eric Anholt <eric at anholt.net> Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch> Cc: Dave Airlie <airlied at redhat.com> Cc: Gerd Hoffmann <kraxel at redhat.com> Cc: virtualization at
2018 May 02
0
[PATCH] drm/qxl: Remove unecessary dma_fence_ops
The trivial enable_signaling implementation matches the default code. v2: Fix up commit message to match patch better (Eric). Cc: Eric Anholt <eric at anholt.net> Reviewed-by: Eric Anholt <eric at anholt.net> Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch> Cc: Dave Airlie <airlied at redhat.com> Cc: Gerd Hoffmann <kraxel at redhat.com> Cc: virtualization at
2018 May 03
0
[PATCH 11/15] drm/qxl: Remove unecessary dma_fence_ops
The trivial enable_signaling implementation matches the default code. v2: Fix up commit message to match patch better (Eric). Cc: Eric Anholt <eric at anholt.net> Reviewed-by: Eric Anholt <eric at anholt.net> Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch> Cc: Dave Airlie <airlied at redhat.com> Cc: Gerd Hoffmann <kraxel at redhat.com> Cc: virtualization at
2018 May 03
1
[PATCH 14/15] drm/virtio: Remove unecessary dma_fence_ops
dma_fence_default_wait is the default now, same for the trivial enable_signaling implementation. Reviewed-by: Eric Anholt <eric at anholt.net> Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch> Cc: David Airlie <airlied at linux.ie> Cc: Gerd Hoffmann <kraxel at redhat.com> Cc: virtualization at lists.linux-foundation.org --- drivers/gpu/drm/virtio/virtgpu_fence.c |
2006 Feb 20
3
Message with multiple attachments
Hello. I am implementing a system that allows you to add multiple attachments to a message. This raises a problem tho. If I try to upload the attachments _BEFORE_ adding the message (thus creating an ID to relate the attachment to), I will need to find a way to store the attachments on a temporary way that will allow me to attach one another later. But, if the user closes the browser before
2012 Mar 06
2
closing file with close(file) *silently*
Hi All, I am writing a function that reads a file in myfile = file('myfile.raw', 'rb') . . . . . close(myfile) No matter what, I get the warning Warning message: closing unused connection 3 (myfile.raw) Since the whole thing is in a function, I'd like to avoid unecessary noise for the user, and I'd like to kill the warning -- without having to mess with global options.
2008 Nov 23
2
ogg dirac granulepos in oggz tools
2008/11/24 David Flynn <davidf+nntp at woaf.net>: > On a slightly unrelated note, i keep hitting the following error in > liboggz when using the oggz tools on an ogg dirac stream: > > /home/davidf/project/liboggz/src/liboggz/oggz.c:202: oggz_close: > Assertion `oggz_dlist_is_empty(oggz->packet_buffer)' failed. > > I'll supply an example file tomorrow if that
2014 Jul 08
2
[LLVMdev] LLVM commit 410f38e01597120b41e406ec1cea69127463f9e5
OK from what I understand, the DAG.getSExtOrTrunc(SetCC, DL, SelectVT) is unecessary and the SelectVT is nto the right type (as it is called with incorrect parameter). Here is a patch so it won't generate a loop. I ran make check and it doesn't look like anything is broken. 2014-07-07 11:36 GMT-07:00 Matt Arsenault <arsenm2 at gmail.com>: > > On Jul 5, 2014, at 7:14 PM,
2003 Dec 09
4
was FXO cards
Hey guys, appreciate the input. Here are some thoughts. ADSI phones are out of the question. This is a business environment, I can't worry about my employees not knowing how to forward calls, answer calls when away from the multiline phone, and no ADSI phone will handle multiple lines that I have found. I would love to put 6 X100P cards in a case and run asterisk on it. but... I
2009 Jul 20
0
[LLVMdev] x86 unwind support[MESSAGE NOT SCANNED]
Duncan Sands wrote: > Hi Mark, Hi Duncan, > >> You are confusing stopping the unwinding at *some* levels or at *all* >> levels. >> Eg. >> invoke >> call >> call >> invoke >> call >> call >> unwind > > the dwarf unwinder only stops and runs user code at the invokes. > It does restore registers
2016 Aug 26
2
Using opus on ATMEL 32-bit RISC microcontroller
Hi, First of all, I'm quite new to opus. I'm trying to use fixed point opus on an ATMEL AT32UC3B0512. I added the opus source into mine sw tree, I trim off code I don't use (eg. arm, x86 folders) It compiles, but the generated image is too big to fit in the flash. Have I any way to reduce the source footprint? (Eg. throw away unecessary files, if there are any..) Thanks, Daniele.
2008 Apr 10
3
Souffleur goals
Silvia, I intend to release a binary on the 26th at most. Supporting at least 2 subtitle formats. Yes, I guess it would be nice to have a page and wiki at a place related to other xiph projects but if that is not possible, I have my own provider or even SF I can put things on. Other then that, I promise that on the next commit, a README file will be commited as well. Mesquita
2004 Aug 06
1
why is there a timeout in _accept_connection (icecast/src/connection.c)
Hi all, I was wondering why there is a timeout (100msec) in the _acception_connection function (icecast/src/connection.c) where it calls the util_timed_wait_for_fd. To me this seems to incur unecessary load on the machine on which the icecast server runs, since each time the timeout expires some more user time is used up by the process. In my particular setup I run an icecast server 24/7, but
2005 Jan 05
1
[PATCH] kinit/kinit.c
A patch for a few more hiccups and trivialities in kinit.c: * The check_path() calls check for "/root" and "/old_root" - I believe that should be "/root" and "/root/old_root". * chdir("/") is recommended after pivot_root() * init_argv[0] isn't set properly to the basename pointed to by char *s - this fix also eliminates six lines of
2009 Jul 20
2
[LLVMdev] x86 unwind support[MESSAGE NOT SCANNED]
Hi Mark, > So who is responsible for (as stated under the invoke description in the > language reference) "ensure that proper cleanup is performed in the case > of either a longjmp or a thrown exception"? the unwinder (however it works) needs to stop at each invoke and run the code in the unwind block of the invoke. I think it is important that the default method of code
2009 Jul 20
4
[LLVMdev] x86 unwind support[MESSAGE NOT SCANNED]
Hi Mark, > You are confusing stopping the unwinding at *some* levels or at *all* > levels. > Eg. > invoke > call > call > invoke > call > call > unwind the dwarf unwinder only stops and runs user code at the invokes. It does restore registers and so forth at every stack frame. This is extra work done at unwind time that reduces the cost