From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-180.mta0.migadu.com (out-180.mta0.migadu.com [91.218.175.180]) (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 4099F3DD51E; Mon, 27 Jul 2026 07:25:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.180 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785137149; cv=none; b=cVwgspZQrnS9WFV6Wa21vI9vKH5K3w4PFS0WQ0yVilmriGnZvl8TBkyZqyLpFFATPzPhzB4E5kW5SpI6x4FKoLbVsXWj9PDiyc5+fy26P9GDGMg+9TPrYiAp4ZV9N8zafGzmZt1mp9PmZHllR2K4cT2hMCAjosWIqXuLEW3TLao= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785137149; c=relaxed/simple; bh=J47sKYVXFsDPGrwWVANqosoLCQ0UZXXSniADY9yNIUE=; h=Mime-Version:Content-Type:Date:Message-Id:Cc:Subject:From:To: In-Reply-To:References; b=nMzf3BpAZwiE7HpexcnNu+rEsowX9s7v5idturF5dM/i1vrqog+VW4sj5BcmOJp/lA3T/F10vskCjmexKmoY6rusddY0KNf6QW2g5AnnUQEIzhZNp/o7Rolb1gjMXyAJ2tb0nCiGZinuX1maAV7yMph5oGsLezSBTUJep6XaRjI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=fi90h6ms; arc=none smtp.client-ip=91.218.175.180 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="fi90h6ms" Precedence: bulk X-Mailing-List: linux-hwmon@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1785137135; 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=Hrajy83uZbAEZ4QXrdneOBkHt4WwSHMSLCICN+iSQXA=; b=fi90h6msLZL7tSozgaiuR1Ijvk7duvQC8bR42WDPPplaECbDFvk4gHk1r29dC5ZTqXL+46 +cyULThIQsp41/GbfUkRxxbXkLgchGfexbfb5EVb+KewWpocx4ruS606a5g+UoEWgikZC6 F+JEFZ+c3Nw7+20SyXYqKVAqwzObms0= Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 27 Jul 2026 00:25:28 -0700 Message-Id: Cc: , , , , , Subject: Re: [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add Sensylink X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Troy Mitchell" To: "Troy Mitchell" , "Rob Herring" , "Krzysztof Kozlowski" , "Conor Dooley" , "Guenter Roeck" , "Paul Walmsley" , "Palmer Dabbelt" , "Albert Ou" , "Alexandre Ghiti" , "Yixun Lan" , "Jonathan Corbet" , "Shuah Khan" In-Reply-To: <20260722-devious-seventh-9859bb3741b3@spud> References: <20260721-ctl2301-v2-0-ef5fb342872a@linux.dev> <20260721-ctl2301-v2-1-ef5fb342872a@linux.dev> <20260721-dill-dab-df15585090d2@spud> <673be23a-2a84-43b7-9be7-a661cf0e7935@roeck-us.net> <20260722-devious-seventh-9859bb3741b3@spud> X-Migadu-Flow: FLOW_OUT > On Tue, Jul 21, 2026 at 10:56:36AM -0700, Guenter Roeck wrote: >> On 7/21/26 08:49, Conor Dooley wrote: >>> On Tue, Jul 21, 2026 at 02:48:27AM -0700, Troy Mitchell wrote: >>>> Add the vendor prefix for Sensylink Microelectronics. >>>> >>>> [...] >>>> >>>> + "^sensylink,.*": >>>> + description: Sensylink Microelectronics Technology Co., Ltd. >>> >>> Googling the company to see what their website is, I seem to see a >>> different name for the company: Shanghai Sensylink Microelectronics Inc= . >>> Their website has that with the Shanghai dropped. >>> >>> Also, probably the commit message should contain >>> Link: https://en.sensylink.com/ >> >> Asking Google search: "Why the two names ? Did they rename themselves at >> some point ?" > > The google search "AI" response was what showed me the different name, > sounds like I should have questioned it some more! > >> [...] >> >> I don't know if Linux has a policy about Legal vs. Marketing names. >> Personally I don't have an opinion. Your call, really. > > I don't know what the policy is, or if there is one, but personally I > wouldn't use the westernised abbreviation since they may decide to rebran= d > that etc and the vendor prefix information should remain static. > > So this is probably fine as-is, just I'd like to see that link added to > their website. Understood. I will keep the current vendor name and add the following link to the commit message in the next version: Link: https://en.sensylink.com/ - Troy