From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.manjaro.org (mail.manjaro.org [116.203.91.91]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 90C2512F5A6; Wed, 14 Feb 2024 18:30:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=116.203.91.91 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707935453; cv=none; b=sFCUsgTVMgJf6sqg6hpwNcjV//QbLjdJodaxWwnoE0FRNNki9VgSYCKxlG85cEv6pbyHEBEtn2hA9qnA8YvZSDCjEGKM7cCKIGJLB5HuI4gkCjo267g8dS4A0hxv2rdWTptcUhbhIcW8ygYretYrv+FY4xJyv1lL7MtkHOph2hY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707935453; c=relaxed/simple; bh=5uP8HuasPE9jjTg8TVWNXGQF/Kh7MKjGojWz/AXkG2Y=; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:Content-Type; b=BmgAfO8OVm5OZC+xU83+hEb+e1EaDe2NSKA04Fsi3cvhuiXpU9NuhmAFULEL0qD2gf3gy4OXGn9U/JQjJq+fG6+kphzF93zVGEclc2huOKkmxbtUtMPuFde7IbsqG+43qTKtDKeMuULcWRTDJetzTHLkQDeplFqsWiC54K3J7Fo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=manjaro.org; spf=pass smtp.mailfrom=manjaro.org; dkim=pass (2048-bit key) header.d=manjaro.org header.i=@manjaro.org header.b=MjznPnCi; arc=none smtp.client-ip=116.203.91.91 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=manjaro.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=manjaro.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=manjaro.org header.i=@manjaro.org header.b="MjznPnCi" Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=manjaro.org; s=2021; t=1707935446; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yBm/TVAwluVa6W1ppxE/9VD5uiTG5c6NeW89/JYMXY0=; b=MjznPnCifzzDeID5hxhRe5HjMuAMYMBfod6hcJaXXeGnbCBQyqGdy0V0yM5MkMuUPJDXae 3yUbZBZOvwjzNhN/gF1r+MvKtUjvueXDXbHJ5jHp5wwOtmmDpfYBwvQ8Gs/0bGPMmWkrxv byOOaaLyeYv/t6OzGbL6LfQ5CA+k3/va0d6nWFzbyJabyL2UExOVXZUX87a4DXlHioSbgd TInaD9VFAlYhn45qzK8+OzoDskmLudnUYBGxgx2wQcqUitJrd1ec4kW3WojXdOBfOT+wDM W5GkNZyizat53+yxu2OMvm1L3pdUY2U3RLZwjPk4g6Fd2aZtdPV3GASLaHwhsg== Date: Wed, 14 Feb 2024 19:30:44 +0100 From: Dragan Simic To: Conor Dooley Cc: Tim Lunn , linux-rockchip@lists.infradead.org, Andy Yan , AngeloGioacchino Del Regno , Chris Morgan , Conor Dooley , Cristian Ciocaltea , David Heidelberg , Heiko Stuebner , Jagan Teki , Krzysztof Kozlowski , Ondrej Jirman , Rob Herring , Tianling Shen , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/4] Fix vendor strings on Rockchip boards In-Reply-To: <20240214-moocher-womanless-21201b67b76d@spud> References: <20240214040731.3069111-1-tim@feathertop.org> <20240214-moocher-womanless-21201b67b76d@spud> Message-ID: X-Sender: dsimic@manjaro.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Authentication-Results: ORIGINATING; auth=pass smtp.auth=dsimic@manjaro.org smtp.mailfrom=dsimic@manjaro.org Hello Conor, On 2024-02-14 19:12, Conor Dooley wrote: > On Wed, Feb 14, 2024 at 03:27:08PM +1100, Tim Lunn wrote: >> On 2/14/24 15:14, Dragan Simic wrote: >> > On 2024-02-14 05:07, Tim Lunn wrote: >> > > A couple of rockchip boards incorrectly list their vendor as Rockchip >> > > when they are in fact not manufactured by Rockchip. >> > > >> > > Fix the vendor strings to correctly list the manufacturer >> > >> > Just checking, have you verified that the old, incorrect "compatible" >> > strings from the board dts files aren't used anywhere in the kernel code, >> > such as in some drivers? >> > >> Yes I checked that, there are no remaining references to the >> old/incorrect >> compatible strings in kernel code > > What about other code? Like a BSD or a bootloader? If nothing is using > them > Acked-by: Conor Dooley I just quickly checked U-Boot and it's fine. > Fixes tags I think wouldn't go amiss, but I'm not expecting a resend > with them.