Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp136370rdb; Thu, 21 Dec 2023 05:12:40 -0800 (PST) X-Google-Smtp-Source: AGHT+IH53kM8zPbKWHRfXqgg6LlG7MNGPeU/PulZZTnkyAH4K28nfsH6RqlzUWCIZxOs2ldT8ZO5 X-Received: by 2002:a05:6e02:19c8:b0:35d:660e:3165 with SMTP id r8-20020a056e0219c800b0035d660e3165mr34956178ill.94.1703164360307; Thu, 21 Dec 2023 05:12:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703164360; cv=none; d=google.com; s=arc-20160816; b=FIMef2MMI0OZnP9ZAm2o6PYhgoDUzqhS2Bp7yjiKC6H5Q7zXW2o15pCyAGW/efMniw BOmUDFjpe12usA6yEXaRyfybAKduDsJtdsSR0T0XyVp/bZMLXvrX6wvuYsghTYLn6iIM sgpE1Tj39BAm5LkxuaYWm8HqlG22Zjc6apEOBLPEFPh/box0qfttGltOA9ozkITn45vZ tDktinEYjPetsxNxd81wdJYJRZh5ab/6MS2FEfTZIOjMmsATOlfx9+FjTsu4OHhLtxe8 6PaPbdFJFU2NeXeyNoF4u4yzqmIQad8POzokAmS4iI6DCr1AMqCPQJLgkiHAI30RtHnP aTfQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=slz2jAIdyfaIXaV1PsekmkmArwzo5cYKmNhd1kYBtXQ=; fh=LgYyUhmYwyrwqJSz7ofvSnk1fUOh4lb2R9hvWGSsrd0=; b=CSDufclfizMn6Sk+TN+l0gY0fy0pyIeFLuKByU77+LsgRHzXzTRLAxbgiOAPS8pT04 SPRNsmIgLIDvM8h+0hHdtYtG0L76RFsCbWrWqf08hcpyuGHoFZT/z2TqWUGAEOjyff0X yhSp5bRoopjRCjFmFupUvZXoYdjIvBOdMdlWJ2kPgqzBB082T7TlCXZy5tFpJMIkXTkt bWsELcmjGcA+j5VR4V5YCYVNcvdceejHD4GwtcqSvUflxzDJlcc6AVolnkggVcW4G8AH m4Jg6D9wI32uhTqGKogjoabiY2hThWH23KmAAvwoCbh+/Zy2dm2DDVxvBIZE23tr75OI nRPA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=S0XNbvUt; spf=pass (google.com: domain of linux-kernel+bounces-8430-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-8430-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from sy.mirrors.kernel.org (sy.mirrors.kernel.org. [147.75.48.161]) by mx.google.com with ESMTPS id o124-20020a634182000000b005cdacf770c2si1592025pga.702.2023.12.21.05.12.39 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 21 Dec 2023 05:12:40 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-8430-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=S0XNbvUt; spf=pass (google.com: domain of linux-kernel+bounces-8430-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-8430-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sy.mirrors.kernel.org (Postfix) with ESMTPS id 3E904B219E5 for ; Thu, 21 Dec 2023 13:10:12 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 93C3673186; Thu, 21 Dec 2023 13:10:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="S0XNbvUt" X-Original-To: linux-kernel@vger.kernel.org Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 B112B73167; Thu, 21 Dec 2023 13:10:06 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D4C8DC433C8; Thu, 21 Dec 2023 13:10:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1703164206; bh=bqwNo3sih6dX67U+J8kDPqDIzx8u7hGCfXZ14KS4L2s=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=S0XNbvUtS54+Og/3j1U1Q525F1VpWrWIOyDcGyyD2ROhi2hlayRacda8jWR27unlQ wjM20cBTpnFpvZGxpwOKlVTziWMCcgc6jh5Uait1KeDRpZvvtWsDTDyncawl8nacra VAzrfCcBik/gHFlbG7DFQw3odW34LAjT/LmbYc3c= Date: Thu, 21 Dec 2023 14:10:03 +0100 From: Greg Kroah-Hartman To: Bagas Sanjaya Cc: Andrew Morton , Jakub Kicinski , Linux Kernel Mailing List , Linux Staging Drivers Subject: Re: "Link in bio" instead of Link:/Closes: trailer Message-ID: <2023122129-twisty-mumble-c667@gregkh> References: <2023122112-rigging-january-7618@gregkh> 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: On Thu, Dec 21, 2023 at 07:57:21PM +0700, Bagas Sanjaya wrote: > On 12/21/23 18:51, Greg Kroah-Hartman wrote: > > On Thu, Dec 21, 2023 at 06:15:50PM +0700, Bagas Sanjaya wrote: > >> Hi all, > >> > >> Let's say that there is a content creator who submits her first kernel > >> patch (touching drivers/staging/ of course to get her feet wet). > >> The patch supposes to fix a reported bug, with appropriate Fixes: tag. > >> But instead of using Link: or Closes: tag to the actual bug report in > >> the patch, she instead writes "Link to the bug report in my bio", as > >> it is the norm in social media world. Here in the context, her bio is > >> LinkedIn profile (IDK if there is a way to add arbitrary link there). > >> The link in LinkedIn profile, when clicked, will list many links > >> (including her usual social media campaigns and of course the bug report), > >> which makes reviewers confused about which link to the bug report she > >> means. In some cases, she may disambiguate by saying in the patch, > >> "Link to the bug report no. 99", to refer to the specific link number. > >> > >> Is such practice a good idea? > > > > No. > > why? Exactly, why? What problem are you trying to solve here that has actually come up in any sort of frequency? "Link: " is something that should be used to point to a well-known and stable reference for any future things, like red hat's bugzilla, or lore.kernel.org. It's not for random social-media link reputation spamming, sorry. The "proper" way to handle this is to have in your Linked-in, or whatever social media site you like, a list of your committed patches in the git.kernel.org tree, don't polute the kernel log please. greg k-h