Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp5817984rwd; Wed, 24 May 2023 07:11:53 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4v/KH0V4PIJOYlJLCcBUHUDLP+nIPJw1q6cSiqCsH5qaDJ6NhX4o0J2WK955O7E2Hf/i4R X-Received: by 2002:a05:6a21:329b:b0:10b:cb77:5403 with SMTP id yt27-20020a056a21329b00b0010bcb775403mr11642226pzb.52.1684937513050; Wed, 24 May 2023 07:11:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684937513; cv=none; d=google.com; s=arc-20160816; b=SM0sPvnpBAIiQAzmUZC8VgBq8SI0fV2MJiAI57kekha4qvHpwEzjB9pIJh2IZcNJiw 1f4LIX0WipCYuBk7X+opHjtkwM9sDYQj/IgR6DcaCs1SvtGi2jAa2YqHbi+YiJmVTVlL FIDQEDHRj4q3j6rI29ljZFh3Kt+0u9dHPDpYIZiNdVyQWsOr7xWwe16PaUpedt83wAoh vOnPv9y0PGzkHj/TvjPb3ejUnz6EREWIVZknSX0WCk/e5ZKLa0IghJyMrJxSyDzGUN19 2m/bGn7jaW18lhAYLOI/Sb9GYnHMHZIad0SrEnEwfqLtK5M8LzUywgkYdli7pEjCQY1m upXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:dkim-signature; bh=+jETYai0NTMaHEoWFiNXrG0rOxzb4UpAuG4arUQ2oeI=; b=VcsHEniQDVhaxwZTot2LNefc3T2WdSLp0yQnYyGfddi4H6aahIxb0HuzSJxDO9Wbz2 05tgpRd7F/vZb1iq2l41OyjvvqHwYp34LUXOuuDh5cbqnPM5h8NSGbcqbm75whiRuYwc DMBk2gOvMdlLOkJWufgNI5zldgLh9bFlieEmhoaRAXMuAjyohAFI6mvkN7DhQATrtYjj Vab1dket6toXTyI+84UoFyW4R2m0CYInOA580T03nHTnjehib2bGg+rhEgD5jfXUi/uc oEPoHKrfD0R4fLB5Z3kEJxJhF5p6+et48mgnZStv83VzSTuzgeiKrZmMtVqpdCUjXQ/8 wkLg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=GDcbKEEh; 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=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j124-20020a636e82000000b0053b928deb7asi2675948pgc.344.2023.05.24.07.11.39; Wed, 24 May 2023 07:11:53 -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=@intel.com header.s=Intel header.b=GDcbKEEh; 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235199AbjEXOBh (ORCPT + 99 others); Wed, 24 May 2023 10:01:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45378 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232374AbjEXOBe (ORCPT ); Wed, 24 May 2023 10:01:34 -0400 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DCAE99E; Wed, 24 May 2023 07:01:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1684936892; x=1716472892; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=JqaNSBpB1Y3By+PIMe1ztMXiAF8ywA/Mfx2FrrbgG6M=; b=GDcbKEEhvrT8qx0grpCTHmzVNKV/UJOfrnDZ8E5mOUgPPy2+VSoIU25K N08II5dCpnBg/S5mJuoevr3cwfpAZ6SLZGr1FaYgdv0uGiZAK/IZ+fs32 /KmSnSp1Yv/3grhY6FHMMXuM/XgIlusd04McB4j3ZjnfhpMy8Ylblyrqi qUXJj0QEmxiYa8ttyTq2P/1KS8vflPT5swQ1BPNt2gVUMuFAOg3ozcRxh IG1q2T/B3/cBNh7gW8A1GlFkg3gFfLGzfR9R8DxL1G/UdZTkrGJSo5yDk UCkjB5Q77E0IfqUnvhG0B+onK62mvToYLs0Lpq/b3wW3c4Ah+O23mBnRh A==; X-IronPort-AV: E=McAfee;i="6600,9927,10720"; a="381816503" X-IronPort-AV: E=Sophos;i="6.00,189,1681196400"; d="scan'208";a="381816503" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 May 2023 07:01:19 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10720"; a="774262059" X-IronPort-AV: E=Sophos;i="6.00,189,1681196400"; d="scan'208";a="774262059" Received: from nwhelanx-mobl.ger.corp.intel.com ([10.252.55.15]) by fmsmga004-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 May 2023 07:01:17 -0700 Date: Wed, 24 May 2023 17:01:15 +0300 (EEST) From: =?ISO-8859-15?Q?Ilpo_J=E4rvinen?= To: Greg Kroah-Hartman cc: linux-serial , LKML , Jiaqing Zhao Subject: Re: [PATCH] serial: 8250_pci: remove unreachable code for ASIX devices In-Reply-To: Message-ID: <62142324-dc90-788a-f040-72ef11192e6@linux.intel.com> References: <20230510142855.256658-1-jiaqing.zhao@linux.intel.com> <2023051343-cringing-junction-54f7@gregkh> <188db6e4-d1de-6643-f6e1-5cb3807b28ee@linux.intel.com> <2023051533-harmonize-ozone-bc72@gregkh> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE 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 Wed, 24 May 2023, Jiaqing Zhao wrote: > On 2023-05-15 11:49, Greg Kroah-Hartman wrote: > > On Mon, May 15, 2023 at 10:36:30AM +0800, Jiaqing Zhao wrote: > >> On 2023-05-13 18:28, Greg Kroah-Hartman wrote: > >>> Please follow the documented Intel kernel developer requirements before > >>> you submit this again, based on the changes that process will require. > >>> > >>> thanks, > >>> > >>> greg k-h > >> Sorry I am unable to find this "Intel kernel developer requirements". Is > >> there any link or contact where I can find this information? Thank you. > > > > Contact the Intel Linux developer team and they will point you at them. > > This is a company-wide requirement, it is odd that your normal "Here is > > how you can contribute to Linux!" training at Intel did not cover it? > > I contacted them and there is no reply so far. Could you please tell me if > there is any general available docs about this or point out what I'm doing > wrong in this patch? Thank you very much. I've pointed him to the right direction (now that I noticed this has just gone on here). -- i.