Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp1057723ybi; Fri, 24 May 2019 16:24:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqy7Vd+uvBE7yV4WnKVmG547TkXNHuXUDog3p/v7x8dqN2DSqhwoQMLNJDmSSoPPUlonuVug X-Received: by 2002:a63:e018:: with SMTP id e24mr25988352pgh.361.1558740284782; Fri, 24 May 2019 16:24:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558740284; cv=none; d=google.com; s=arc-20160816; b=kGctG3KgKD7S/4pIY7TwBAFlPOgqT4ljk7KEaoz1lZrwHHo7ftB4LdqSZjmBtwlRzD t/fssmvgvWFX2cNnbFjfkBgtI9PPXeadnUqxnbbEjLIGVF9Cctc2Uj7pSAROV1JzRrak s9wmFW79LJzp7gwjpGBufXtN5tJ3/eEUX95F/tvC0o/7TKJQjpJ9A1gQPuQFV0/Uz2ix ClR9q68FRF7/OeVxvfUNaKk+G9u9xVK+LK/nY/190quozWRGMUK0sXk+XSmua3GmFyOX y4Z3TS5wuptAvHBKxDnLmqyJfxOH2CLiDPaX6Btv9oaRYbBIRoV96CQAnbYy245vwcjA CLeQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=XBfCjz3L7g28JeGLcJlNP/XerD1I63TBTPztLXL3giU=; b=gI/zepTy293gmEsp90f0nLW/KrnWdGc1C9mL3aqxJ38LRljVc9R91wMJ/kFpAOgf17 TBO/WhjSE5XMu0ZP0c5mrxDGt+wYgryGtEI5ju/aKAePiDLGIuOuidxSWwA1dna55FJ3 CFbwmXGpdIG3mLiRgphgtcYrYb6EEJRMBgVTOehMZ0mJ8PmUZIxD3BXILa5R6voSi8j6 brsvC04ABmibA7FPUrs7aMgV4l30gAtb7SRk92g+5VOBfXMiShSEOEi9ozeY+nsa/OzZ 9mYSJgJK/51pE0wZzT42P4Q4IlPtnkPuSP1D5o9j0/nrbtb7OzcrFLPNsf5NHtaqx+j4 0aAA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=UjBwr46C; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h61si1363713plb.256.2019.05.24.16.24.29; Fri, 24 May 2019 16:24:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=UjBwr46C; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726213AbfEXXVk (ORCPT + 99 others); Fri, 24 May 2019 19:21:40 -0400 Received: from merlin.infradead.org ([205.233.59.134]:55760 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725853AbfEXXVk (ORCPT ); Fri, 24 May 2019 19:21:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=XBfCjz3L7g28JeGLcJlNP/XerD1I63TBTPztLXL3giU=; b=UjBwr46CW891EN4AnXcME7qDhs 5Q4ULMrRQs49bZjXQ8GaqFsEtWBiEmr1qTDWaFAaUqyEFupl8gdDN9yMqqNCfCHCDiHN0UdDRDLHv 8RLgVBcOW90b3CZ5TaHcAWh24yr9UsyGn1UGU3VCzs02DX/701h71xogjD9udP6YS+7SOV9K4xFLE QqbmDibTo825+Iz+R0NFO9idrP5lgrCmQoL2eciTuWTh8HY4H+MR2dod6F13TQOxuRpc5ASzf2XrU ZYAR/FtGfTZbna0tayzncpt7BxXhlKS0CyRMkhsfof6hOARRFx0ri7jRXUDWvlHEOor/cOBbMd2jE OFaU2SSQ==; Received: from static-50-53-52-16.bvtn.or.frontiernet.net ([50.53.52.16] helo=midway.dunlab) by merlin.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1hUJVK-00079M-DV; Fri, 24 May 2019 23:21:38 +0000 Subject: Re: [A General Question] What should I do after getting Reviewed-by from a maintainer? To: Gen Zhang , akpm@linux-foundation.org Cc: linux-kernel@vger.kernel.org References: <20190523011723.GA15242@zhanggen-UX430UQ> From: Randy Dunlap Message-ID: <7510e8a7-3567-fc22-d8e3-6d6142c06ff3@infradead.org> Date: Fri, 24 May 2019 16:21:36 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190523011723.GA15242@zhanggen-UX430UQ> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/22/19 6:17 PM, Gen Zhang wrote: > Hi Andrew, > I am starting submitting patches these days and got some patches > "Reviewed-by" from maintainers. After checking the > submitting-patches.html, I figured out what "Reviewed-by" means. But I > didn't get the guidance on what to do after getting "Reviewed-by". > Am I supposed to send this patch to more maintainers? Or something else? > Thanks > Gen > [Yes, I am not Andrew. ;] Patches should be sent to a maintainer who is responsible for merging changes for the driver or $arch or subsystem. And they should also be Cc-ed to the appropriate mailing list(s) and source code author(s), usually [unless they are no longer active]. Some source files have author email addresses in them. Or in a kernel git tree, you can use "git log path/to/source/file.c" to see who has been making & merging patches to that file.c. Probably the easiest thing to do is run ./scripts/get_maintainer.pl and it will try to tell you who to send the patch to. HTH. -- ~Randy