Searched hist:1.129 (Results 1 - 25 of 573) sorted by relevance

1234567891011>>

/src/tests/kernel/kqueue/
H A Dt_oneshot.c1.1 Sat Oct 23 18:46:26 GMT 2021 thorpej Fix a regression introduced in kern_event.c,v 1.129 that would cause
"udata" to get clobbered on ONESHOT events, and add a unit test for it.
Reported by martin@ (manifested in his case as a KASSERT() firing when
running unit tests in COMPAT_NETBSD32).

H A Dt_sig.c1.4 Sun Oct 10 18:11:31 GMT 2021 thorpej branches: 1.4.2; 1.4.4;
The knotes for EVFILT_SIGNAL and EVFILT_PROC are maintained on a single
per-process list, and kern_event.c,v 1.129 has several KASSERT()s in
various code paths that process this list related to the mixing of these
two knote types. This new unit test is designed specifically to exercise
those KASSERT()s and thus validate their assumptions.

H A DMakefile1.9 Sat Oct 23 18:46:26 GMT 2021 thorpej Fix a regression introduced in kern_event.c,v 1.129 that would cause
"udata" to get clobbered on ONESHOT events, and add a unit test for it.
Reported by martin@ (manifested in his case as a KASSERT() firing when
running unit tests in COMPAT_NETBSD32).

/src/tests/usr.bin/xlint/lint1/
H A Dd_alignof.c1.4 Thu May 12 00:18:35 GMT 2022 rillig lint: fix support for __alignof__, add support for __alignof

Broken since lex.c 1.129 from yesterday.

1.3 Thu May 12 00:09:44 GMT 2022 rillig tests/lint: adjust tests to reflect missing support of __alignof__

The change in lex.c 1.129 attempted to add support for __alignof, in
addition to the existing support for __alignof__. It failed by removing
support for __alignof__, while allowing the plain 'alignof' instead.

H A Dmsg_014.c1.7 Thu May 12 00:18:35 GMT 2022 rillig lint: fix support for __alignof__, add support for __alignof

Broken since lex.c 1.129 from yesterday.

1.6 Thu May 12 00:09:44 GMT 2022 rillig tests/lint: adjust tests to reflect missing support of __alignof__

The change in lex.c 1.129 attempted to add support for __alignof, in
addition to the existing support for __alignof__. It failed by removing
support for __alignof__, while allowing the plain 'alignof' instead.

/src/sys/ufs/lfs/
H A Dulfs_quota1.c1.10 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes:

ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8
ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7
ufs_lookup.c 1.126 does not apply to lfs
ufs_lookup.c 1.127 we already have
ufs_lookup.c 1.128 does not apply to lfs
ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19
ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7
ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8
ufs_quota2.c 1.36 we have equivalent changes for
ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5
ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6
ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19
ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20
ufs_vnops.c 1.221 was superseded by later changes
ufs_vnops.c 1.222 got fixed independently in lfs

H A Dulfs_dirhash.c1.16 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes:

ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8
ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7
ufs_lookup.c 1.126 does not apply to lfs
ufs_lookup.c 1.127 we already have
ufs_lookup.c 1.128 does not apply to lfs
ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19
ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7
ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8
ufs_quota2.c 1.36 we have equivalent changes for
ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5
ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6
ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19
ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20
ufs_vnops.c 1.221 was superseded by later changes
ufs_vnops.c 1.222 got fixed independently in lfs

H A Dulfs_extattr.c1.9 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes:

ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8
ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7
ufs_lookup.c 1.126 does not apply to lfs
ufs_lookup.c 1.127 we already have
ufs_lookup.c 1.128 does not apply to lfs
ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19
ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7
ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8
ufs_quota2.c 1.36 we have equivalent changes for
ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5
ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6
ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19
ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20
ufs_vnops.c 1.221 was superseded by later changes
ufs_vnops.c 1.222 got fixed independently in lfs

H A Dlfs_rename.c1.18 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes:

ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8
ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7
ufs_lookup.c 1.126 does not apply to lfs
ufs_lookup.c 1.127 we already have
ufs_lookup.c 1.128 does not apply to lfs
ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19
ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7
ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8
ufs_quota2.c 1.36 we have equivalent changes for
ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5
ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6
ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19
ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20
ufs_vnops.c 1.221 was superseded by later changes
ufs_vnops.c 1.222 got fixed independently in lfs

/src/sys/dev/mii/
H A Dmiidevs.h1.129 Mon Jul 03 08:29:22 GMT 2017 msaitoh branches: 1.129.4;
Regen.

1.129 Mon Jul 03 08:29:22 GMT 2017 msaitoh branches: 1.129.4;
Regen.

/src/sys/compat/linux/arch/i386/
H A Dlinux_machdep.c1.129 Sat Jun 30 22:54:33 GMT 2007 dsl branches: 1.129.6; 1.129.8; 1.129.12;
Call fp->f_ops->fo_ioctl() directly (not by sys_ioctl() for LINUX_VT_GETMODE
and LINUX_VT_SETMODE. One fewer use of the stackgap.

1.129 Sat Jun 30 22:54:33 GMT 2007 dsl branches: 1.129.6; 1.129.8; 1.129.12;
Call fp->f_ops->fo_ioctl() directly (not by sys_ioctl() for LINUX_VT_GETMODE
and LINUX_VT_SETMODE. One fewer use of the stackgap.

1.129 Sat Jun 30 22:54:33 GMT 2007 dsl branches: 1.129.6; 1.129.8; 1.129.12;
Call fp->f_ops->fo_ioctl() directly (not by sys_ioctl() for LINUX_VT_GETMODE
and LINUX_VT_SETMODE. One fewer use of the stackgap.

1.129 Sat Jun 30 22:54:33 GMT 2007 dsl branches: 1.129.6; 1.129.8; 1.129.12;
Call fp->f_ops->fo_ioctl() directly (not by sys_ioctl() for LINUX_VT_GETMODE
and LINUX_VT_SETMODE. One fewer use of the stackgap.

/src/sys/arch/hp300/hp300/
H A Dtrap.c1.129 Sun Mar 04 05:59:50 GMT 2007 christos branches: 1.129.2; 1.129.4; 1.129.10;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

1.129 Sun Mar 04 05:59:50 GMT 2007 christos branches: 1.129.2; 1.129.4; 1.129.10;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

1.129 Sun Mar 04 05:59:50 GMT 2007 christos branches: 1.129.2; 1.129.4; 1.129.10;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

1.129 Sun Mar 04 05:59:50 GMT 2007 christos branches: 1.129.2; 1.129.4; 1.129.10;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

/src/sys/arch/dreamcast/conf/
H A DGENERIC1.129 Thu Sep 14 07:58:39 GMT 2017 mrg branches: 1.129.2; 1.129.4;
clean up COMPAT_* options for native netbsd code:
- new series of files that are useful for saying "i want everything
since netbsd 1.4", etc.
- use the fact COMPAT_* options have future dependancies to remove
many redundant options.

removes about 3000 lines total across kernel configuration files.
tested about 30 random kernels in the changed list.

1.129 Thu Sep 14 07:58:39 GMT 2017 mrg branches: 1.129.2; 1.129.4;
clean up COMPAT_* options for native netbsd code:
- new series of files that are useful for saying "i want everything
since netbsd 1.4", etc.
- use the fact COMPAT_* options have future dependancies to remove
many redundant options.

removes about 3000 lines total across kernel configuration files.
tested about 30 random kernels in the changed list.

1.129 Thu Sep 14 07:58:39 GMT 2017 mrg branches: 1.129.2; 1.129.4;
clean up COMPAT_* options for native netbsd code:
- new series of files that are useful for saying "i want everything
since netbsd 1.4", etc.
- use the fact COMPAT_* options have future dependancies to remove
many redundant options.

removes about 3000 lines total across kernel configuration files.
tested about 30 random kernels in the changed list.

/src/share/man/man7/
H A Dhier.71.129 Thu Mar 01 06:37:40 GMT 2018 snj branches: 1.129.2; 1.129.4;
remove reference to /usr/X11R6

1.129 Thu Mar 01 06:37:40 GMT 2018 snj branches: 1.129.2; 1.129.4;
remove reference to /usr/X11R6

1.129 Thu Mar 01 06:37:40 GMT 2018 snj branches: 1.129.2; 1.129.4;
remove reference to /usr/X11R6

/src/sys/miscfs/procfs/
H A Dprocfs_vnops.c1.129 Thu Feb 02 00:29:24 GMT 2006 christos branches: 1.129.2; 1.129.4; 1.129.6; 1.129.8;
PR/32692: Matthew Mondor: linux compatibility in /proc/self should point
directly to the directory containing the pid instead of pointing to
/proc/curproc, because some programs rely on calling readlink on /proc/self
to get the pid.

1.129 Thu Feb 02 00:29:24 GMT 2006 christos branches: 1.129.2; 1.129.4; 1.129.6; 1.129.8;
PR/32692: Matthew Mondor: linux compatibility in /proc/self should point
directly to the directory containing the pid instead of pointing to
/proc/curproc, because some programs rely on calling readlink on /proc/self
to get the pid.

1.129 Thu Feb 02 00:29:24 GMT 2006 christos branches: 1.129.2; 1.129.4; 1.129.6; 1.129.8;
PR/32692: Matthew Mondor: linux compatibility in /proc/self should point
directly to the directory containing the pid instead of pointing to
/proc/curproc, because some programs rely on calling readlink on /proc/self
to get the pid.

1.129 Thu Feb 02 00:29:24 GMT 2006 christos branches: 1.129.2; 1.129.4; 1.129.6; 1.129.8;
PR/32692: Matthew Mondor: linux compatibility in /proc/self should point
directly to the directory containing the pid instead of pointing to
/proc/curproc, because some programs rely on calling readlink on /proc/self
to get the pid.

1.129 Thu Feb 02 00:29:24 GMT 2006 christos branches: 1.129.2; 1.129.4; 1.129.6; 1.129.8;
PR/32692: Matthew Mondor: linux compatibility in /proc/self should point
directly to the directory containing the pid instead of pointing to
/proc/curproc, because some programs rely on calling readlink on /proc/self
to get the pid.

/src/sys/dev/raidframe/
H A Drf_driver.c1.129 Fri May 27 22:48:24 GMT 2011 yamt branches: 1.129.4; 1.129.10; 1.129.14; 1.129.16;
don't forget to destroy mutex.

1.129 Fri May 27 22:48:24 GMT 2011 yamt branches: 1.129.4; 1.129.10; 1.129.14; 1.129.16;
don't forget to destroy mutex.

1.129 Fri May 27 22:48:24 GMT 2011 yamt branches: 1.129.4; 1.129.10; 1.129.14; 1.129.16;
don't forget to destroy mutex.

1.129 Fri May 27 22:48:24 GMT 2011 yamt branches: 1.129.4; 1.129.10; 1.129.14; 1.129.16;
don't forget to destroy mutex.

1.129 Fri May 27 22:48:24 GMT 2011 yamt branches: 1.129.4; 1.129.10; 1.129.14; 1.129.16;
don't forget to destroy mutex.

/src/sys/nfs/
H A Dnfs_serv.c1.129 Fri Jul 27 10:03:58 GMT 2007 yamt branches: 1.129.4; 1.129.6; 1.129.8; 1.129.10;
stop nfs tick when we have nothing to do.

1.129 Fri Jul 27 10:03:58 GMT 2007 yamt branches: 1.129.4; 1.129.6; 1.129.8; 1.129.10;
stop nfs tick when we have nothing to do.

1.129 Fri Jul 27 10:03:58 GMT 2007 yamt branches: 1.129.4; 1.129.6; 1.129.8; 1.129.10;
stop nfs tick when we have nothing to do.

1.129 Fri Jul 27 10:03:58 GMT 2007 yamt branches: 1.129.4; 1.129.6; 1.129.8; 1.129.10;
stop nfs tick when we have nothing to do.

1.129 Fri Jul 27 10:03:58 GMT 2007 yamt branches: 1.129.4; 1.129.6; 1.129.8; 1.129.10;
stop nfs tick when we have nothing to do.

/src/sys/miscfs/fdesc/
H A Dfdesc_vnops.c1.129 Fri May 26 14:21:01 GMT 2017 riastradh branches: 1.129.8; 1.129.10;
Make VOP_RECLAIM do the last unlock of the vnode.

VOP_RECLAIM naturally has exclusive access to the vnode, so having it
locked on entry is not strictly necessary -- but it means if there
are any final operations that must be done on the vnode, such as
ffs_update, requiring exclusive access to it, we can now kassert that
the vnode is locked in those operations.

We can't just have the caller release the last lock because some file
systems don't use genfs_lock, and require the vnode to remain valid
for VOP_UNLOCK to work, notably unionfs.

1.129 Fri May 26 14:21:01 GMT 2017 riastradh branches: 1.129.8; 1.129.10;
Make VOP_RECLAIM do the last unlock of the vnode.

VOP_RECLAIM naturally has exclusive access to the vnode, so having it
locked on entry is not strictly necessary -- but it means if there
are any final operations that must be done on the vnode, such as
ffs_update, requiring exclusive access to it, we can now kassert that
the vnode is locked in those operations.

We can't just have the caller release the last lock because some file
systems don't use genfs_lock, and require the vnode to remain valid
for VOP_UNLOCK to work, notably unionfs.

1.129 Fri May 26 14:21:01 GMT 2017 riastradh branches: 1.129.8; 1.129.10;
Make VOP_RECLAIM do the last unlock of the vnode.

VOP_RECLAIM naturally has exclusive access to the vnode, so having it
locked on entry is not strictly necessary -- but it means if there
are any final operations that must be done on the vnode, such as
ffs_update, requiring exclusive access to it, we can now kassert that
the vnode is locked in those operations.

We can't just have the caller release the last lock because some file
systems don't use genfs_lock, and require the vnode to remain valid
for VOP_UNLOCK to work, notably unionfs.

/src/sys/arch/sparc64/sparc64/
H A Ddb_interface.c1.129 Wed Jun 22 05:50:47 GMT 2011 mrg branches: 1.129.2; 1.129.6;
there's no fr_arg[6] or fr_arg[7] -- they're called fr_fp and fr_pc.
use the right names and avoid some array bounds violations picked up
by GCC 4.5. it's a real bug, but the code would have been generated
correctly for the sparc* ABIs.

1.129 Wed Jun 22 05:50:47 GMT 2011 mrg branches: 1.129.2; 1.129.6;
there's no fr_arg[6] or fr_arg[7] -- they're called fr_fp and fr_pc.
use the right names and avoid some array bounds violations picked up
by GCC 4.5. it's a real bug, but the code would have been generated
correctly for the sparc* ABIs.

1.129 Wed Jun 22 05:50:47 GMT 2011 mrg branches: 1.129.2; 1.129.6;
there's no fr_arg[6] or fr_arg[7] -- they're called fr_fp and fr_pc.
use the right names and avoid some array bounds violations picked up
by GCC 4.5. it's a real bug, but the code would have been generated
correctly for the sparc* ABIs.

/src/sys/arch/newsmips/conf/
H A DGENERIC1.129 Sun Nov 16 16:01:42 GMT 2014 manu branches: 1.129.2; 1.129.12;
Remove unused extended attributes kernel options

As Masao Uebayashi pointed to me, UFS_EXTATTR_AUTOSTART, LFS_EXTATTR_AUTOSTART
and UFS_EXTATTR_AUTOCREATE are not used anywhere in the code. Remove them
as they have been obsolete for a long time:
UFS_EXTATTR_AUTOSTART was replaced by mount -o extattr
LFS_EXTATTR_AUTOSTART was created to match obsolete UFS_EXTATTR_AUTOSTART
UFS_EXTATTR_AUTOCREATE was replaced by sysctl vfs.ffs.extattr_autocreate

1.129 Sun Nov 16 16:01:42 GMT 2014 manu branches: 1.129.2; 1.129.12;
Remove unused extended attributes kernel options

As Masao Uebayashi pointed to me, UFS_EXTATTR_AUTOSTART, LFS_EXTATTR_AUTOSTART
and UFS_EXTATTR_AUTOCREATE are not used anywhere in the code. Remove them
as they have been obsolete for a long time:
UFS_EXTATTR_AUTOSTART was replaced by mount -o extattr
LFS_EXTATTR_AUTOSTART was created to match obsolete UFS_EXTATTR_AUTOSTART
UFS_EXTATTR_AUTOCREATE was replaced by sysctl vfs.ffs.extattr_autocreate

1.129 Sun Nov 16 16:01:42 GMT 2014 manu branches: 1.129.2; 1.129.12;
Remove unused extended attributes kernel options

As Masao Uebayashi pointed to me, UFS_EXTATTR_AUTOSTART, LFS_EXTATTR_AUTOSTART
and UFS_EXTATTR_AUTOCREATE are not used anywhere in the code. Remove them
as they have been obsolete for a long time:
UFS_EXTATTR_AUTOSTART was replaced by mount -o extattr
LFS_EXTATTR_AUTOSTART was created to match obsolete UFS_EXTATTR_AUTOSTART
UFS_EXTATTR_AUTOCREATE was replaced by sysctl vfs.ffs.extattr_autocreate

/src/sys/dev/ic/
H A Dncr53c9x.c1.129 Mon Aug 20 00:32:30 GMT 2007 tsutsui branches: 1.129.2; 1.129.4;
KNF, ANSIfy, TAB/space cosmetics.

1.129 Mon Aug 20 00:32:30 GMT 2007 tsutsui branches: 1.129.2; 1.129.4;
KNF, ANSIfy, TAB/space cosmetics.

1.129 Mon Aug 20 00:32:30 GMT 2007 tsutsui branches: 1.129.2; 1.129.4;
KNF, ANSIfy, TAB/space cosmetics.

/src/sys/arch/amiga/amiga/
H A Damiga_init.c1.129 Mon Nov 26 22:58:24 GMT 2012 rkujawa branches: 1.129.36; 1.129.38;
Try to make z3rambd less crude. Also support BigRamPlus, FastLane Z3 RAM and
DKB3128.

1.129 Mon Nov 26 22:58:24 GMT 2012 rkujawa branches: 1.129.36; 1.129.38;
Try to make z3rambd less crude. Also support BigRamPlus, FastLane Z3 RAM and
DKB3128.

1.129 Mon Nov 26 22:58:24 GMT 2012 rkujawa branches: 1.129.36; 1.129.38;
Try to make z3rambd less crude. Also support BigRamPlus, FastLane Z3 RAM and
DKB3128.

/src/sys/arch/amiga/conf/
H A DGENERIC.in1.129 Sun Nov 16 16:01:40 GMT 2014 manu branches: 1.129.2; 1.129.4;
Remove unused extended attributes kernel options

As Masao Uebayashi pointed to me, UFS_EXTATTR_AUTOSTART, LFS_EXTATTR_AUTOSTART
and UFS_EXTATTR_AUTOCREATE are not used anywhere in the code. Remove them
as they have been obsolete for a long time:
UFS_EXTATTR_AUTOSTART was replaced by mount -o extattr
LFS_EXTATTR_AUTOSTART was created to match obsolete UFS_EXTATTR_AUTOSTART
UFS_EXTATTR_AUTOCREATE was replaced by sysctl vfs.ffs.extattr_autocreate

1.129 Sun Nov 16 16:01:40 GMT 2014 manu branches: 1.129.2; 1.129.4;
Remove unused extended attributes kernel options

As Masao Uebayashi pointed to me, UFS_EXTATTR_AUTOSTART, LFS_EXTATTR_AUTOSTART
and UFS_EXTATTR_AUTOCREATE are not used anywhere in the code. Remove them
as they have been obsolete for a long time:
UFS_EXTATTR_AUTOSTART was replaced by mount -o extattr
LFS_EXTATTR_AUTOSTART was created to match obsolete UFS_EXTATTR_AUTOSTART
UFS_EXTATTR_AUTOCREATE was replaced by sysctl vfs.ffs.extattr_autocreate

1.129 Sun Nov 16 16:01:40 GMT 2014 manu branches: 1.129.2; 1.129.4;
Remove unused extended attributes kernel options

As Masao Uebayashi pointed to me, UFS_EXTATTR_AUTOSTART, LFS_EXTATTR_AUTOSTART
and UFS_EXTATTR_AUTOCREATE are not used anywhere in the code. Remove them
as they have been obsolete for a long time:
UFS_EXTATTR_AUTOSTART was replaced by mount -o extattr
LFS_EXTATTR_AUTOSTART was created to match obsolete UFS_EXTATTR_AUTOSTART
UFS_EXTATTR_AUTOCREATE was replaced by sysctl vfs.ffs.extattr_autocreate

/src/sys/dev/usb/
H A Dukbd.c1.129 Thu Sep 26 07:25:31 GMT 2013 skrll branches: 1.129.4; 1.129.6;
Remove usbd_do_request_async. It's callback was calling usbd_free_xfer
from softint context.

Adjust callers appropriately

- usbd_clear_endpoint_stall_async is already triggered via a
usb_task, so simply call usbd_do_request.

- uhidev_set_report_async had one caller in ukbd_set_leds.
Convert this usage to use usb_task as well.

Discussed with mrg@

1.129 Thu Sep 26 07:25:31 GMT 2013 skrll branches: 1.129.4; 1.129.6;
Remove usbd_do_request_async. It's callback was calling usbd_free_xfer
from softint context.

Adjust callers appropriately

- usbd_clear_endpoint_stall_async is already triggered via a
usb_task, so simply call usbd_do_request.

- uhidev_set_report_async had one caller in ukbd_set_leds.
Convert this usage to use usb_task as well.

Discussed with mrg@

1.129 Thu Sep 26 07:25:31 GMT 2013 skrll branches: 1.129.4; 1.129.6;
Remove usbd_do_request_async. It's callback was calling usbd_free_xfer
from softint context.

Adjust callers appropriately

- usbd_clear_endpoint_stall_async is already triggered via a
usb_task, so simply call usbd_do_request.

- uhidev_set_report_async had one caller in ukbd_set_leds.
Convert this usage to use usb_task as well.

Discussed with mrg@

/src/sys/sys/
H A Dexec.h1.129 Mon Dec 14 00:48:35 GMT 2009 matt branches: 1.129.2; 1.129.4;
Merge from matt-nb5-mips64

1.129 Mon Dec 14 00:48:35 GMT 2009 matt branches: 1.129.2; 1.129.4;
Merge from matt-nb5-mips64

1.129 Mon Dec 14 00:48:35 GMT 2009 matt branches: 1.129.2; 1.129.4;
Merge from matt-nb5-mips64

Completed in 123 milliseconds

1234567891011>>