On Thu, Jul 07, 2022 at 07:59:29PM +0200, Kristof Provost wrote:
> On 7 Jul 2022, at 19:00, Steve Kargl wrote:
>
> > The fix in
> > 37f604b49d4a seems rather questionable especially given
> > that there is no comment about why the macro is expanded
> > to a zero-trip loop.
> >
> I’m not sure how I
On 7 Jul 2022, at 19:00, Steve Kargl wrote:
On Thu, Jul 07, 2022 at 10:37:40AM -0600, Warner Losh wrote:
On Thu, Jul 7, 2022 at 10:37 AM Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
Thanks, but
root[216] git cherry-pick -n 37f604b49d4a
fatal: bad revision '37f604b49d4a'
root[217] p
On Thu, Jul 7, 2022 at 11:21 AM Kyle Evans wrote:
> On Thu, Jul 7, 2022 at 10:01 AM Steve Kargl
> wrote:
> >
> > On Thu, Jul 07, 2022 at 10:37:40AM -0600, Warner Losh wrote:
> > > On Thu, Jul 7, 2022 at 10:37 AM Steve Kargl <
> > > s...@troutmask.apl.washington.edu> wrote:
> > >
> > > > Thanks,
On Thu, Jul 7, 2022 at 10:01 AM Steve Kargl
wrote:
>
> On Thu, Jul 07, 2022 at 10:37:40AM -0600, Warner Losh wrote:
> > On Thu, Jul 7, 2022 at 10:37 AM Steve Kargl <
> > s...@troutmask.apl.washington.edu> wrote:
> >
> > > Thanks, but
> > >
> > > root[216] git cherry-pick -n 37f604b49d4a
> > > fata
On Thu, Jul 07, 2022 at 10:37:40AM -0600, Warner Losh wrote:
> On Thu, Jul 7, 2022 at 10:37 AM Steve Kargl <
> s...@troutmask.apl.washington.edu> wrote:
>
> > Thanks, but
> >
> > root[216] git cherry-pick -n 37f604b49d4a
> > fatal: bad revision '37f604b49d4a'
> > root[217] pwd
> > /usr/src
>
>
>
On Thu, Jul 7, 2022 at 10:37 AM Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
> Thanks, but
>
> root[216] git cherry-pick -n 37f604b49d4a
> fatal: bad revision '37f604b49d4a'
> root[217] pwd
> /usr/src
git fetch maybe?
Warner
>
--
> steve
>
> On Thu, Jul 07, 2022 at 11:24:47AM -04
Thanks, but
root[216] git cherry-pick -n 37f604b49d4a
fatal: bad revision '37f604b49d4a'
root[217] pwd
/usr/src
--
steve
On Thu, Jul 07, 2022 at 11:24:47AM -0400, Ryan Stone wrote:
> You could "git cherry-pick -n 37f604b49d4a; git restore --unstaged
> sys/net/vnet.h" to apply the fix to your lo
Or you could cherry-pick the fix. When you update git pull --rebase will
automatically
drop it when you rebase past that spot. Or if you have a branch, you can do
the same
to the branch and when you rebase past the fix, it will automatically drop.
Warner
On Thu, Jul 7, 2022 at 9:25 AM Ryan Stone
You could "git cherry-pick -n 37f604b49d4a; git restore --unstaged
sys/net/vnet.h" to apply the fix to your local tree without committing
it or leaving it staged for commit.
On Thu, Jul 7, 2022 at 10:50 AM Steve Kargl
wrote:
>
> On Thu, Jul 07, 2022 at 10:38:43AM -0400, Ryan Stone wrote:
> > Okay
On Thu, Jul 07, 2022 at 10:38:43AM -0400, Ryan Stone wrote:
> Okay, update your tree and it should be fixed then.
Is it possible to pull just that fix? I spent part of
yesterday building world, and contrary to popular belief,
not all hardware contain a 32-core uber-fast ryzen cpu.
Can people ple
Okay, update your tree and it should be fixed then.
Yes, I do.
Deleting the line allows to code to compile.
--
steve
On Thu, Jul 07, 2022 at 08:24:47AM -0400, Ryan Stone wrote:
> Do you have VNET disabled in your kernel config? I believe that this
> was fixed by 37f604b49d4a.
>
> On Thu, Jul 7, 2022 at 1:07 AM Steve Kargl
> wrote:
> >
> > -st
Do you have VNET disabled in your kernel config? I believe that this
was fixed by 37f604b49d4a.
On Thu, Jul 7, 2022 at 1:07 AM Steve Kargl
wrote:
>
> -std=iso9899:1999 -Werror /usr/src/sys/netinet/tcp_input.c
> --- modules-all ---
> /usr/src/sys/netpfil/ipfw/ip_dn_io.c:674:4: error: 'continue' s
On Sun, Jul 07, 2013 at 11:51:01PM +0200, Claude Buisson wrote:
C> On 07/07/2013 22:05, Gleb Smirnoff wrote:
C> > On Fri, Jul 05, 2013 at 08:32:06AM -0700, Steve Kargl wrote:
C> > S> On Fri, Jul 05, 2013 at 05:03:38PM +0400, Gleb Smirnoff wrote:
C> > S> > On Tue, Jul 02, 2013 at 08:45:16PM -0700, S
On 07/07/2013 22:05, Gleb Smirnoff wrote:
On Fri, Jul 05, 2013 at 08:32:06AM -0700, Steve Kargl wrote:
S> On Fri, Jul 05, 2013 at 05:03:38PM +0400, Gleb Smirnoff wrote:
S> > On Tue, Jul 02, 2013 at 08:45:16PM -0700, Steve Kargl wrote:
S> > S> On Tue, Jul 02, 2013 at 10:51:57PM -0230, Jonathan And
On Fri, Jul 05, 2013 at 08:32:06AM -0700, Steve Kargl wrote:
S> On Fri, Jul 05, 2013 at 05:03:38PM +0400, Gleb Smirnoff wrote:
S> > On Tue, Jul 02, 2013 at 08:45:16PM -0700, Steve Kargl wrote:
S> > S> On Tue, Jul 02, 2013 at 10:51:57PM -0230, Jonathan Anderson wrote:
S> > S> > On Tuesday, 2 July 20
On Fri, Jul 05, 2013 at 05:03:38PM +0400, Gleb Smirnoff wrote:
> On Tue, Jul 02, 2013 at 08:45:16PM -0700, Steve Kargl wrote:
> S> On Tue, Jul 02, 2013 at 10:51:57PM -0230, Jonathan Anderson wrote:
> S> > On Tuesday, 2 July 2013 at 22:16, Steve Kargl wrote:
> S> > > It seems that
> S> > >
> S> > >
On Tue, Jul 02, 2013 at 08:45:16PM -0700, Steve Kargl wrote:
S> On Tue, Jul 02, 2013 at 10:51:57PM -0230, Jonathan Anderson wrote:
S> > On Tuesday, 2 July 2013 at 22:16, Steve Kargl wrote:
S> > > It seems that
S> > >
S> > > # Enable FreeBSD7 compatibility syscalls
S> > > options COMPAT_FREEBSD7
S>
On Tue, Jul 02, 2013 at 10:51:57PM -0230, Jonathan Anderson wrote:
> On Tuesday, 2 July 2013 at 22:16, Steve Kargl wrote:
> > It seems that
> >
> > # Enable FreeBSD7 compatibility syscalls
> > options COMPAT_FREEBSD7
> >
> > is required in a kernel config file. If it is mandatory to
> > have this
On Tuesday, 2 July 2013 at 22:16, Steve Kargl wrote:
> It seems that
>
> # Enable FreeBSD7 compatibility syscalls
> options COMPAT_FREEBSD7
>
> is required in a kernel config file. If it is mandatory to
> have this option on FreeBSD 10, it may be appropriate to
> expand the comment to
>
>
> # E
On Tue, Jul 02, 2013 at 05:35:35PM -0700, Steve Kargl wrote:
> /usr/src/sys/kern/sysv_shm.c: At top level:
> /usr/src/sys/kern/sysv_shm.c:1044: error: 'freebsd7_shmctl' undeclared here
> (not in a function)
> *** Error code 1
It seems that
# Enable FreeBSD7 compatibility syscalls
options
21 matches
Mail list logo
