Hello,
Sorry if this is the wrong list, but I found a couple of branch
revisions in file src/sys/dev/midi.c which produce an error when
clicking "annotate" link in cvsweb.
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/midi.c?annotate=1.40.6.1
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys
Hello,
In ehci_alloc_itd_chain(), no need to compute uframes if nframes
is zero and function would return early.
- Michael
Index: src/sys/dev/usb/ehci.c
===
RCS file: /cvs/src/sys/dev/usb/ehci.c,v
retrieving revision 1.200
diff -u
Hi,
markus@ pointed out that it makes no sense to call pcb lookup from
pf during packet forwarding.
While there remove a useless ifp parameter form ip_output_ipsec_send().
ok?
bluhm
Index: net/pf.c
===
RCS file: /data/mirror/openb
On 11/21/17 16:31, Mark Kettenis wrote:
The diff below exposes voltage regulators as sensors. This makes it
easy to look at the current settings of these regulators. The
downside is that these aren't really sensors as the voltages are not
actually measured.
The functionality is optional; cal
The diff below exposes voltage regulators as sensors. This makes it
easy to look at the current settings of these regulators. The
downside is that these aren't really sensors as the voltages are not
actually measured.
The functionality is optional; callers can pass NULL in the
regulator_register
Hi,
While writing tests for the Emacs editing mode in ksh I discovered some
potential errors in the manual:
- Sync the order of key bindings in emacs.c with the manual
- ^W is bound to delete-word-backward and not kill-region which is
mentioned in emacs.c. I don't know the full history here...
On Sun, Nov 12, 2017 at 10:43:46PM +0100, Klemens Nanni wrote:
> On Sun, Nov 12, 2017 at 09:04:22PM +, Robert Peichaer wrote:
> > Hmm. I see.
> >
> > The {add,del,no,pre}_path functions are in ksh.kshrc since when it was
> > imported 21 years ago. If they would be used in ksh.kshrc or anywhere
> Date: Tue, 21 Nov 2017 17:57:41 +0100 (CET)
> From: Mark Kettenis
>
> So it seems clang honours .align 0 (meaning things should be
> byte-aligned) leading to SIGBUS when compiling libc with clang. Diff
> below turns the relevant ones into .align 2 and removes unecessary
> directives from Ovfor
So it seems clang honours .align 0 (meaning things should be
byte-aligned) leading to SIGBUS when compiling libc with clang. Diff
below turns the relevant ones into .align 2 and removes unecessary
directives from Ovfork.S.
I think arm64 suffers from the same problem; I will fix it in a
separate d