From nobody Mon Aug 28 22:54:10 2023 X-Original-To: dev-commits-src-main@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RZQq508Tsz4s37D for ; Mon, 28 Aug 2023 22:54:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RZQq44jmQz4Xj1 for ; Mon, 28 Aug 2023 22:54:24 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-x12c.google.com with SMTP id 2adb3069b0e04-50078e52537so5726880e87.1 for ; Mon, 28 Aug 2023 15:54:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1693263262; x=1693868062; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QLObXTKqUP7/oR4qjk6lbWXe5tUDb6T0DR7Afa5m1t8=; b=Oi9GPh55mDPCUq94HWfYNkOwo1s9e3pVOLg77OS38RPNCosN5RzcmOcdpehf5rgZ3u soxAQBpeSJVOZhXygTEiE2+itaaVfDHerF/pRMzP3eWGMACuJlZBWwW9B3t2aelHbLXN 0ZtDZbx9E5LgAmp5p5ssAKrm5Dtlvjxc++ydId2RRrZ9PubG5MdbWNl8kLbAYxQp/YW/ erRua7N4X4Nhfs1fDq5MNBmQAM5cOH93LP88RpFOix6ci5sK7irhJ8fOCAskHr8jvThJ tu5P6ZUUAh9JWHj3sP0zvhr68SMNoIBDfa8GQag2DFbCv7GesRGIORCO/z/oAN4JgRPG Q+SA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693263262; x=1693868062; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QLObXTKqUP7/oR4qjk6lbWXe5tUDb6T0DR7Afa5m1t8=; b=hSeMrO8VqVhTykQDqr5LMJJjhjZOe/LBOM54o9dhVHa0UotuFBa7h+6WV+XfJO64+3 wbFRGLB8A+IpL2ReEbNIZHJRtFC5wbLvtJ9a9HNYz9deXyG7TE743QnHsDXjpR9hlQNp BOwKuc+cFbKgpnsyoW3x/DDuG8zhyWT7efQr4DoTWezd2rtJhx8UGESGe+rfB7K2aO3G d1lyuacgIz5y3NoBuOZBT2SxhzMaSVpUwLk48M9/H+65o8GWBoYMNjz589dp0EilS7Ad sDM9UdlGBvUUC+QfPfFlOY4cxXMpwxNzdHijC5ilxytpU0p3tHBqcC8S7lIn66iD+CMB +5/g== X-Gm-Message-State: AOJu0Yyd8+C2fHsiVzua2sDWv1K3Z4MIQUiMYFRrXNiwESKu9kq6fY0R 6NcELjbJwtVuirpsLG1J+lgeT5O/Cos9BBS90RDWA3qUnQP06qlo X-Google-Smtp-Source: AGHT+IGu6sVFPxIX7SUsZ+6swrmC1Bdh8OqS4uhPBwgBaouJjphb07MQYuYYUwrIxx4Xb40V3jaDHqShj7WCGcRGdEE= X-Received: by 2002:a05:6512:3da7:b0:4fe:3724:fdae with SMTP id k39-20020a0565123da700b004fe3724fdaemr24876374lfv.66.1693263262212; Mon, 28 Aug 2023 15:54:22 -0700 (PDT) List-Id: Commit messages for the main branch of the src repository List-Archive: https://lists.freebsd.org/archives/dev-commits-src-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-src-main@freebsd.org X-BeenThere: dev-commits-src-main@freebsd.org MIME-Version: 1.0 References: <8874149F-C8FF-4EDD-AECC-23E95D3A1C62.ref@yahoo.com> <8874149F-C8FF-4EDD-AECC-23E95D3A1C62@yahoo.com> In-Reply-To: <8874149F-C8FF-4EDD-AECC-23E95D3A1C62@yahoo.com> From: Warner Losh Date: Mon, 28 Aug 2023 16:54:10 -0600 Message-ID: Subject: Re: git: af93fea71038 - main - timerfd: Move implementation from linux compat to sys/kern To: Mark Millard Cc: "" Content-Type: multipart/alternative; boundary="000000000000417cdc0604039384" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4RZQq44jmQz4Xj1 --000000000000417cdc0604039384 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Aug 28, 2023, 4:37 PM Mark Millard wrote: > Warner Losh wrote on > Date: Mon, 28 Aug 2023 21:49:16 UTC : > > > On Mon, Aug 28, 2023 at 3:27=E2=80=AFPM Kyle Evans = wrote: > > > > > . . . > > > > > > > . . . > > > > And I totally acknowledge there were some issues with the import. I > > accept responsibility for not catching them. thankfully, Jake is workin= g > > to address them and we have enough time before 14.0. I'm also making > > notes for what to do differently next time. One is clearly to loop Alex= ey > > into the process: I didn't think about it before the commit, but in > > hindsight > > it's really something I should have done. > > > > > I'll note that https://www.freebsd.org/releases/14.0R/schedule/ > makes no distinction for KBI breakage types of changes vs. KBI > changes in general for its listed KBI restriction: > > QUOTE > Code slush begins / KBI freeze 4 August 2023 3 August 2023 > . . . Additionally, there can be no changes to the KBI > until main is branched to stable/14. > END QUOTE > > I'd not know if the wording is stronger than the intent. It is > difficult to word things for a complicated intent. But, for > all I know, the wording could match the intent. > Several other additions happened in that time frame. I've always read it as "to established" before KBIs. But this is really more an ABI addition to userland. No K involved. Warner =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > --000000000000417cdc0604039384 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Aug 28, 2023, 4:37 PM Mark Millard <marklmi@yahoo.com> wrote:
Warner Losh <imp_at_bsdimp.com= > wrote on
Date: Mon, 28 Aug 2023 21:49:16 UTC :

> On Mon, Aug 28, 2023 at 3:27=E2=80=AFPM Kyle Evans <kevans@freebsd.= org> wrote:
>
> > . . .
> >
>
> . . .
>
> And I totally acknowledge there were some issues with the import. I > accept responsibility for not catching them. thankfully, Jake is worki= ng
> to address them and we have enough time before 14.0. I'm also maki= ng
> notes for what to do differently next time. One is clearly to loop Ale= xey
> into the process: I didn't think about it before the commit, but i= n
> hindsight
> it's really something I should have done.
>


I'll note that https://www.freebsd.or= g/releases/14.0R/schedule/
makes no distinction for KBI breakage types of changes vs. KBI
changes in general for its listed KBI restriction:

QUOTE
Code slush begins / KBI freeze 4 August 2023 3 August 2023
. . . Additionally, there can be no changes to the KBI
until main is branched to stable/14.
END QUOTE

I'd not know if the wording is stronger than the intent. It is
difficult to word things for a complicated intent. But, for
all I know, the wording could match the intent.

Several other additions happ= ened in that time frame. I've always read it as "to established&qu= ot; before KBIs.

But thi= s is really more an ABI addition to userland.=C2=A0 No K involved.

Warner
=3D=3D=3D
Mark Millard
marklmi at yahoo.com

--000000000000417cdc0604039384--