Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2909184ybi; Mon, 10 Jun 2019 00:25:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqyMQPj9pWr1/kRuIFKEOALj/HcCKsNzbDH8Hrt2XNzG7KxuWKw+gLLhvqzaibRxXzuBCjBM X-Received: by 2002:a17:90a:fa12:: with SMTP id cm18mr19779390pjb.137.1560151546132; Mon, 10 Jun 2019 00:25:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560151546; cv=none; d=google.com; s=arc-20160816; b=IFkaTj0vdhqILw6iS7f7z+9k+q6zC5yW5gYQ6CkC30dAvvKvN/Mk01zCHBcjahHUz2 Bfj2UfFo1xXEl5ZI2sfDt0i6oSq8faoV2wEgjQGgPpyK2OJNMh5nwksnjnsQGJJ4uP1s LwxVgLrVn6cqD3b/MNVrQ9J1rjJectmAkwnqr7toasfcelGscpHPdYucMXbxrvTqasGt blyYIfl/dFHT5T10M4kP02U6gZV+KYfoyqQEw+25wfsQ2gO/vVg3AX6pzzquqHOPintW vk95HQPWzA1Kgbt4qrUMmDKosIP3nfiUGVVoo+G3HitQ6u7DgBqtd4BnatiAyX5SfUi2 RsyA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=SahIcG95Of81ytu4rDgTq5VZNifywyLP8hYn8NFPAUk=; b=busdoMWtdRwBRoxA8jaWX4eg6lBi+SpnCrTAJsM0A0w//px7hlVwlz2PEjCHgIRRa+ uPzgJ+8DmWgY9VCEMuHl9rUA5t5+Z0ldHbc3Y2XDqPp6bheA/p4GoCqlEm3frgZzoYca H2+JjoV3L7nct4SWBjBVVFc+W/8o6AsIwqgh5zdg75ebM/S2T2DhTJANxr0PIdf/SFfR pu9XDxPZ/f1XT5/MdQHHzUM4FT9PckRXoJrBoAZa8KBNUXO9ivv9I+AnQBSjd9Aw6YnB 44bXilfAW5PwUfbLXq026UlWQdUy2WxpwZm4uDqLYFBgwJ0i7p9R3joOYxkx9TOlWJRd oAAg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ffnUIqbY; 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 f12si4156585plo.100.2019.06.10.00.25.30; Mon, 10 Jun 2019 00:25:46 -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=pass header.i=@kernel.org header.s=default header.b=ffnUIqbY; 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 S2387953AbfFJHZ0 (ORCPT + 99 others); Mon, 10 Jun 2019 03:25:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:51682 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387541AbfFJHZZ (ORCPT ); Mon, 10 Jun 2019 03:25:25 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 997A7207E0; Mon, 10 Jun 2019 07:25:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560151525; bh=wu4ufzhepp5a61PnVAmbtYOPDerdxY/PIVog+ksjNtg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ffnUIqbY5OY7dIM1A+KJOm1E+oFvKHKlywaEu+ZoAhlavVbft5swhILTYUxkhc41u /j8ZodhhA7uRmIFiAN/tVJGsX9n93Dyo5JxKnlNcvojLViW1jU1KILJGB1Ogz/OBS6 R0bZelg/GdFwzPi8AzBaCiccVKgfQI3DmGszkaXY= Date: Mon, 10 Jun 2019 09:25:21 +0200 From: Greg KH To: Nishka Dasgupta Cc: devel@driverdev.osuosl.org, benniciemanuel78@gmail.com, linux-kernel@vger.kernel.org, hardiksingh.k@gmail.com Subject: Re: [PATCH] staging: rtl8723bs: core: rtw_mlme_ext.c: Remove unused variables Message-ID: <20190610072521.GA20470@kroah.com> References: <20190607071123.28193-1-nishkadg.linux@gmail.com> <20190609110206.GD30671@kroah.com> <74fd5a83-0f60-baae-a65f-bbc0cd9f4ad0@gmail.com> <20190610054927.GA13124@kroah.com> <7554e171-360f-f0a8-5742-9a60e4a1cc2d@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7554e171-360f-f0a8-5742-9a60e4a1cc2d@gmail.com> User-Agent: Mutt/1.12.0 (2019-05-25) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 10, 2019 at 12:44:05PM +0530, Nishka Dasgupta wrote: > On 10/06/19 11:19 AM, Greg KH wrote: > > On Mon, Jun 10, 2019 at 10:08:21AM +0530, Nishka Dasgupta wrote: > > > On 09/06/19 4:32 PM, Greg KH wrote: > > > > On Fri, Jun 07, 2019 at 12:41:23PM +0530, Nishka Dasgupta wrote: > > > > > Remove variables that are declared and assigned values but not otherwise > > > > > used. > > > > > Issue found with Coccinelle. > > > > > > > > > > Signed-off-by: Nishka Dasgupta > > > > > --- > > > > > drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 9 --------- > > > > > 1 file changed, 9 deletions(-) > > > > > > > > You sent me 8 patches for this driver, yet only 2 were ordered in a > > > > series. I have no idea what order to apply these in :( > > > > > > > > Please resend them _all_ in a numbered patch series so I have a chance > > > > to get this correct. > > > > > > Yes, I can do that. Who do I send the patch series to in that case? The > > > maintainers list is slightly different for each file, and most of the > > > patches in this driver are for different and unrelated files (except, I > > > think, the two that I did send as a patch series). Do I combine the > > > maintainers lists and send the entire patch series to everyone listed as a > > > maintainer for any one of the patches in it? > > > > The maintainer and mailing list is the same for all of the files in a > > single driver. If not, then something is wrong. > > I'm using get_maintainers.pl with no arguments, and for rtl8723bs, I am > getting a lot of different mailing lists. > E.g > For core/rtw_ieee80211.c, I'm getting the following list: > Greg Kroah-Hartman > Michael Straube > Andy Shevchenko > Hardik Singh Rathore > Payal Kshirsagar > Nishka Dasgupta > devel@driverdev.osuosl.org (open list:STAGING SUBSYSTEM) > linux-kernel@vger.kernel.org (open list) > > Which is not the same as for core/rtw_mlme_ext.c (the current patch). > > > And yes, you can combine the list of people if you wish but be sure you > > are not just randomly including people who happened to touch the driver > > "last". > > Okay, I'll combine then. But is there any metric I should be using to filter > the output of get_maintainer.pl? Currently I'm running it with no arguments > and just adding everyone. Look at the "role" that each person has. Here is the output of get_maintainer.pl when I run it on the first file above: $ ./scripts/get_maintainer.pl --file drivers/staging/rtl8723bs/core/rtw_ieee80211.c Greg Kroah-Hartman (supporter:STAGING SUBSYSTEM,commit_signer:16/16=100%) Michael Straube (commit_signer:14/16=88%,authored:14/16=88%,added_lines:43/59=73%,removed_lines:114/130=88%) Payal Kshirsagar (commit_signer:1/16=6%,authored:1/16=6%,added_lines:3/59=5%) Hardik Singh Rathore (commit_signer:1/16=6%,authored:1/16=6%,added_lines:13/59=22%,removed_lines:13/130=10%) Andy Shevchenko (commit_signer:1/16=6%) devel@driverdev.osuosl.org (open list:STAGING SUBSYSTEM) linux-kernel@vger.kernel.org (open list) That shows that "Greg Kroah-Hartman" is a reviewer for this subsystem, Michael and Payal and Hardik and Andy have all submitted patches "recently", and then devel@ is the mailing list for the patches to be sent to. So, just include the maintainer and the mailing list and you will be fine. No need to bother lkml with staging patches, nor the people who last sent cleanup patches. hope this helps, greg k-h