From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6721633893A; Thu, 27 Nov 2025 15:56:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=156.67.10.101 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764258989; cv=none; b=LbgGHkWpIR/jnJJO7UHY2U+Q75K90+RBMVZcPtAGKROVzFT5AtcQ9OmAdh+WDdTKt0c5tZ+8txUPQ8psaakWWAc614ZbXcT6bQrXBdtKCk1OiMobvK4mdsZ3nLMFnmRwEZ4cbjZgFaGYbiBmYKb+Xn2ScyMYKnLLMEBTFD6oAiY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764258989; c=relaxed/simple; bh=tV6Mko4OcH+BRs/hwl+PIoVt+JtdqFrzfqVvSDARuu0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=afNv6pYbrY0AnCebvCYt+y3ecQ4U89mBIEv/Pjc7W1hXx9oNh9QT+BTdSmZvkndC7IUIdQQT2q3c2+JW2mlv/ShisX8kX7orFNnmf8sM/JcfN9WRGpJZWU3h0g5VNW0CkSfHbHlfnWC+0RL+a263c17QEX5eCEeiMCt8j1B5NU0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch; spf=pass smtp.mailfrom=lunn.ch; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b=AyyGsmkv; arc=none smtp.client-ip=156.67.10.101 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="AyyGsmkv" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=76FJT75Kjp6ENeuKI3CQYQWgK2lcdUAiw2gY9LhCcoc=; b=AyyGsmkvks1nnkGd1W5pyGGNPb yJKQe9ApPw+DNqiWRINv0KnW4D9S8XfJstMBR/Eao77Glyr02m/InixHitansVmVgQaCVa1pTJwFg JaJEq7OxyNBnGFFS0cy8N4IQ+WAOQofmMPXk+Waa9goI3pBA7k5iI4HA992fMhjq5bKI=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1vOeLw-00FHEe-VQ; Thu, 27 Nov 2025 16:56:16 +0100 Date: Thu, 27 Nov 2025 16:56:16 +0100 From: Andrew Lunn To: Buday Csaba Cc: Jakub Kicinski , Heiner Kallweit , Russell King , "David S. Miller" , Eric Dumazet , Paolo Abeni , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next 1/1] net: mdio: reset PHY before attempting to access ID register Message-ID: <54f2a7ff-640d-4a9d-bfc9-5190f295f466@lunn.ch> References: <6cb97b7bfd92d8dc1c1c00662114ece03b6d2913.1764069248.git.buday.csaba@prolan.hu> <20251125184335.040f015e@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: > c) what about using EXPORT_SYMBOL_FOR_MODULES() on the problematic > functions? Are there any objections against it? > This type of export is rarely used in the kernel, so I am uncertain > about that. Is using it on functions declared in private headers > also discouraged? Rather than _FOR_MODULES, how about using a namespace. https://docs.kernel.org/core-api/symbol-namespaces.html#how-to-use-symbols-exported-in-namespaces Add a name space "NET_PHY_CORE_ONLY", and put these symbols into that name space. We should notice any driver importing that namespace and reject it. Andrew