From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.0 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 90E22C4320E for ; Mon, 30 Aug 2021 20:17:10 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 49A2C60F5B for ; Mon, 30 Aug 2021 20:17:10 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 49A2C60F5B Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=challenge-bot.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1mKnhf-0005vF-Mz; Mon, 30 Aug 2021 16:16:23 -0400 Received: from challenge-bot.com ([2602:fffa:fff:108a:0:16:3e15:92b8]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1mHLSX-00089z-Tu for kernelnewbies@kernelnewbies.org; Sat, 21 Aug 2021 03:30:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=challenge-bot.com; s=20180430; h=Content-Type:MIME-Version:Message-ID: Subject:To:From:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=6UaXtYV4wt14aWk4KNbXmBb28Rhag4Q4sTZ6n5pEi/4=; b=ZbtTka91QfMk9KNx/7nNOqZ7Gm UxKcPWCKN7Mrgd8OH2K/CT8qX+66wmjSzWY12DImc9WthgIzHn/LacPBSAT45BDVsSO1k1nML9VSv BKFXhPgEZ8g9HxA70PhZRqunudxkvCJ41gAa/JLexUEhMA//nkvA0ta4XmLnpkBQP1A4=; Received: from ozzloy by challenge-bot.com with local (Exim 4.92) (envelope-from ) id 1mHLSV-0005PL-CJ for kernelnewbies@kernelnewbies.org; Sat, 21 Aug 2021 00:30:27 -0700 Date: Sat, 21 Aug 2021 00:30:27 -0700 From: daniel watson To: kernelnewbies@kernelnewbies.org Subject: how do you find the subsystem of a file? Message-ID: <20210821073027.GD18204@challenge-bot.com> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-Mailman-Approved-At: Mon, 30 Aug 2021 16:16:21 -0400 X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org i wrote a patch that got rejected because it did not apply cleanly to the tree of greg kh https://lkml.org/lkml/2021/8/18/304 the file i modified is drivers/staging/rtl8723bs/include/rtl8192c_recv.h get_maintainer.pl gave me the list of emails to send the patch to, and i used it for that purpose. the file Documentation/process/submitting-patches.rst says to see the T: entry for the subsystem in MAINTAINERS to find the right tree to base the patch on. i tried searching through MAINTAINERS and found that there are a few subsystems that start with RTL8*. greg kh is listed a few times in MAINTAINERS, so i'm not able to find the exact tree to start with by looking for the maintainer. is there a systematic way of finding the subsystem, given a file? in addition, how do i know what branch to use? the T: entries have a repo, but not a branch name. thanks! :wq, danny _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies