From: daniel watson <ozzloy@challenge-bot.com>
To: kernelnewbies@kernelnewbies.org
Subject: Re: how do you find the subsystem of a file?
Date: Sat, 21 Aug 2021 16:19:31 -0700 [thread overview]
Message-ID: <20210821231931.GB7414@challenge-bot.com> (raw)
In-Reply-To: <20210821073027.GD18204@challenge-bot.com>
On Sat, Aug 21, 2021 at 12:30:27AM -0700, daniel watson wrote:
> 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
answering my own question,
the output of
git log --oneline -1 <path>
should have the subsystem listed at the beginning.
thanks!
C-x C-c, danny
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-08-21 23:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 7:30 how do you find the subsystem of a file? daniel watson
2021-08-21 23:19 ` daniel watson [this message]
2021-08-22 0:23 ` Valdis Klētnieks
2021-09-01 6:37 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210821231931.GB7414@challenge-bot.com \
--to=ozzloy@challenge-bot.com \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).