Received-SPF: pass (google.com: domain of linux-kernel+bounces-179205-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: Elizabeth Figura <zfigura@codeweavers.com>
To: linux-kernel@vger.kernel.org,
 Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject:
 Re: [PATCH] misc: ntsync: mark driver as "broken" to prevent from building
Date: Tue, 14 May 2024 16:45:13 -0500
Message-ID: <12433821.O9o76ZdvQC@watership>
In-Reply-To: <2024051450-abrasion-swizzle-550b@gregkh>
References: <2024051450-abrasion-swizzle-550b@gregkh>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Tuesday, May 14, 2024 2:16:51=E2=80=AFAM CDT Greg Kroah-Hartman wrote:
> The ntsync code is only partially enabled in the kernel at this point in
> time, creating the device node and that's about it.  Don't confuse
> systems that expect to see a working ntsync interface by teasing it with
> this basic structure at this point in time, so mark the code as "broken"
> so that it is not built and enabled just yet.
>=20
> Once the rest of the code is accepted, this will be reverted so that the
> driver can be correctly built and used, but for now, this is the safest
> way forward.

Reviewed-by: Elizabeth Figura <zfigura@codeweavers.com>

=2D-

I was even thinking of suggesting something like this myself. Sorry for
taking so long to get the rest of the patches into acceptable shape...