Received: by 2002:ac0:e350:0:0:0:0:0 with SMTP id g16csp285262imn; Fri, 29 Jul 2022 06:53:49 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tPLwUuwgWiJo6kTQoBJI54l/xXx163AE4OYROy4yUMKKZbRkhfgUWKf6WbpUju3k01WNIc X-Received: by 2002:a05:6402:5412:b0:435:5997:ccb5 with SMTP id ev18-20020a056402541200b004355997ccb5mr3526024edb.167.1659102829024; Fri, 29 Jul 2022 06:53:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659102829; cv=none; d=google.com; s=arc-20160816; b=BLlYwjjMdwHjiH44zYI42CHAUFGhWn1QKjsg4Mzdj7PYgLZZA4IV+6KRVvyd/zdQ1L 8o5TcV8eB1qJW2xwGn3JOk6k5aUiWaZLw2IxsBUZrYsG2+QVhnkPR+YRfSpVx7umx9z2 uN7e7YTlhd0HOP9IgZ0qgyZIP+I5SKSP18Kzg/hN175NwP8Wq2jaU7UdMk38U2dHRtQ2 xtn9IwUu8nE+18tnOo0RaxxqsAhMFduOO0aO7d2S+8vsp4RdJgwIXs76NINdsM6YxPuZ Pz5Gn84eK9cs+GGfHiL4t1f4BFyRcmEaQUf6GQEFkCB1tg0l0eEJNGlhDUnb+RImA32a 6glQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=cKiPIazQ94BDYqqDCIA6j4RlQGYjcrjqVfsPPSFKhD4=; b=uriH0GQPzucyiv03+ay/EJ0FQNw7I4mnNfjwU8rf+lN/Wqk80cnb561ZfEBzqB5yFI OJZ3rZfeB+0TN78xS3MRTpJ/5I1+5aiRZqVpXWJKsnmJgnp2+xVF/V/J3rEDbRrdm46/ U5fWFYsTUmieRqTk7zrdothrJREePBD6G8tbbpjD1fwko1tdpyHJMLG4pqmlwb+SpxVa Oh8xEG+nVp98OQTaewLkzgC6bHDLCQ141tg3KPf7+ombUabzry+0N8wRpCtYr7frGyaT qUTuqcw4KqH0j/fenLXuqMRn200jrik0FAM8SkOa88XW1R2q6CZeICb9mlEbWYfXhXmZ zAoA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=VGi+dc17; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id vl2-20020a170907b60200b00726a675c097si3398829ejc.337.2022.07.29.06.53.23; Fri, 29 Jul 2022 06:53:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=VGi+dc17; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236635AbiG2NkY (ORCPT + 99 others); Fri, 29 Jul 2022 09:40:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56450 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235451AbiG2NkW (ORCPT ); Fri, 29 Jul 2022 09:40:22 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C06111180C; Fri, 29 Jul 2022 06:40:20 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 5D90861F4C; Fri, 29 Jul 2022 13:40:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 378BCC433D6; Fri, 29 Jul 2022 13:40:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1659102019; bh=0OSNx2MkLas4Uvqd32G0wnYPkqwVOT8GaNmWvKmuHQQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=VGi+dc17KprHrHpJ2H3pemHcy6c4NC2hK7DSwjiSMUlz7QJR6WZotCcvqZ3F4AJi6 TeNza7yxrPninBAzA3R1493aUPyUVtu2uh0m620SFqZT8jpoQm/L1xmOLgOiDJZK4P WEDImwpAf+c6DSV8QEh7d/H+OOZetid+l9lWc1mU= Date: Fri, 29 Jul 2022 15:40:16 +0200 From: Greg Kroah-Hartman To: Tom Lendacky Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-doc-tw-discuss@lists.sourceforge.net, Jonathan Corbet , Alex Shi , Yanteng Si , Hu Haowen Subject: Re: [PATCH] docs: embargoed-hardware-issues: remove bouncing AMD contact info Message-ID: References: <20220729100745.2225558-1-gregkh@linuxfoundation.org> <7da72334-f3ea-fe73-b4b4-bec97ae15946@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7da72334-f3ea-fe73-b4b4-bec97ae15946@amd.com> X-Spam-Status: No, score=-7.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 29, 2022 at 07:59:42AM -0500, Tom Lendacky wrote: > On 7/29/22 05:20, Greg Kroah-Hartman wrote: > > On Fri, Jul 29, 2022 at 12:07:45PM +0200, Greg Kroah-Hartman wrote: > > > The current AMD contact info in the embargoed-hardware-issues.rst file > > > is bouncing as an invalid address, so remove it from the documentation. > > > > > > At this point in time, the kernel community has no way to contact AMD > > > for any hardware-specific problems. Hopefully they can resolve this > > > issue soon, or maybe they just don't have any hardware bugs and do not > > > need to worry about this. > > > > > > Cc: Jonathan Corbet > > > Cc: Alex Shi > > > Cc: Yanteng Si > > > Cc: Hu Haowen > > > Signed-off-by: Greg Kroah-Hartman > > > --- > > > Documentation/process/embargoed-hardware-issues.rst | 2 +- > > > .../translations/zh_CN/process/embargoed-hardware-issues.rst | 2 +- > > > .../translations/zh_TW/process/embargoed-hardware-issues.rst | 2 +- > > > 3 files changed, 3 insertions(+), 3 deletions(-) > > > > > > diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst > > > index 95999302d279..a8c38e1c40dc 100644 > > > --- a/Documentation/process/embargoed-hardware-issues.rst > > > +++ b/Documentation/process/embargoed-hardware-issues.rst > > > @@ -244,7 +244,7 @@ disclosure of a particular issue, unless requested by a response team or by > > > an involved disclosed party. The current ambassadors list: > > > ============= ======================================================== > > > - AMD Tom Lendacky > > > + AMD > > > > Wait, Tom, is this just the wrong email address for you? And the one > > above I used in the To: the correct one? > > Wow, yes, I can't believe I made that mistake and haven't noticed it! You > are correct, it should be thomas.lendacky@amd.com. Ok, let me go fix this up and change the address in the files and redo this patch. thanks, greg k-h