On Sat, Nov 19, 2022 at 12:03:59PM +, Mikolaj Kucharski wrote:
> Kind reminder.
>
> Below diff also at:
>
> https://marc.info/?l=openbsd-tech=166806412910623=2
>
> This is diff by Noah Meier with small changes by me.
>
>
> On Thu, Nov 10, 2022 at 07:14:11AM +, Mikolaj Kucharski wrote:
On Fri, Dec 23, 2022 at 2:46 PM Abel Abraham Camarillo Ojeda <
acam...@verlet.org> wrote:
> Forgot to mention I don't think this is a regression, just started to use
> hibernate/unhibernate more often lately.
> But I think I can reproduce this at least since 6.8 (the first that I
> installed to
On Fri, Dec 23, 2022 at 03:03:15PM +, Stuart Henderson wrote:
> Overall imho this is too much churn to do in huge swathes across the
> tree.
>
> Fixes for spelling/grammar in comments etc are often more usually
> done by people working on a particular part of the tree or trying to
>
On Fri, Dec 23, 2022 at 1:41 PM Bodie wrote:
> On Fri Dec 23, 2022 at 8:19 PM CET, Abel Abraham Camarillo Ojeda wrote:
> > Hi to all,
> >
> > Sometimes my lenovo L470 won't dim the screen via F5/F6 or be able to
> > suspend/hibernate again after resuming from unhibernation. Also `apm`
> will
>
On Fri Dec 23, 2022 at 8:19 PM CET, Abel Abraham Camarillo Ojeda wrote:
> Hi to all,
>
> Sometimes my lenovo L470 won't dim the screen via F5/F6 or be able to
> suspend/hibernate again after resuming from unhibernation. Also `apm` will
> show the values from before the hibernate and won't update
Hi to all,
Sometimes my lenovo L470 won't dim the screen via F5/F6 or be able to
suspend/hibernate again after resuming from unhibernation. Also `apm` will
show the values from before the hibernate and won't update again, specially
battery info.
Any ideas how can I gather more info when I get
> Date: Fri, 23 Dec 2022 08:37:43 -0600
> From: Scott Cheloha
>
> The blocking futex operation is called FUTEX_WAIT. I think "ftxwait"
> is literally the perfect wmesg.
>
> "fsleep" is a lot less obvious.
>
> ok?
Well, I know what "fsleep" is since it has been around for a while.
I'd have to
> +++ usr.bin/ctfconv/parse.c 22 Dec 2022 21:15:27 -
> @@ -72,7 +72,7 @@ RB_HEAD(itype_tree, itype) itypet[CTF_K
> */
> struct isymb_tree isymbt;
>
> -struct itype *void_it; /* no type is emited for void */
> +struct itype *void_it; /*
Hi Dave,
* Dave Voutila wrote:
> While working back and forth with dlg@ on his idea of adding in async
> task queues to vmd devices, he started to introduce a cleaner way to
> handle virtqueues. In short, we can just track the host virtual address
> and read/write to that location.
>
> This has
The blocking futex operation is called FUTEX_WAIT. I think "ftxwait"
is literally the perfect wmesg.
"fsleep" is a lot less obvious.
ok?
Index: sys_futex.c
===
RCS file: /cvs/src/sys/kern/sys_futex.c,v
retrieving revision 1.21
OK, I've looked through the other 50% of the original diff, (I've not looked
at the new one).
Comments in-line:
On Thu, Dec 22, 2022 at 06:31:23PM -0500, Paul Tagliamonte wrote:
> Index: lib/libssl/test/pkits-test.pl
> ===
> RCS
Dave Voutila writes:
> While working back and forth with dlg@ on his idea of adding in async
> task queues to vmd devices, he started to introduce a cleaner way to
> handle virtqueues. In short, we can just track the host virtual address
> and read/write to that location.
>
> This has the
This one has been irking me for some time. At the moment when decoding a
ber message there is no way for br_application to indicate that the
tag/type is unrecognised and if br_application is not set we default to
BER_TYPE_NULL. In basically all cases any wrong encoding should be
caught by
13 matches
Mail list logo
