From: Your Name <alb3rt0.m3rciai@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
devel@driverdev.osuosl.org, forest@alittletooquiet.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: vt6655: refactor camelcase uCurrRSSI to current_rssi
Date: Fri, 19 Nov 2021 19:51:41 +0100 [thread overview]
Message-ID: <20211119185141.GA396725@bulldog> (raw)
In-Reply-To: <YZeYsip9CD8YkKgl@kroah.com>
> What caused you to pick that one?
My mistake :(
I was reading "Submitting patches: the essential guide
to getting your code into the kernel" and I was confuse dby this line
"See the T: entry for the subsystem in the MAINTAINERS file to find
that tree, or simply ask the maintainer if the tree is not listed
there." supposing that master branch was the correct one.
I'm moving on "staging-next" branch as you suggest.
Regards,
Alberto
prev parent reply other threads:[~2021-11-19 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 20:27 [PATCH v3] staging: vt6655: refactor camelcase uCurrRSSI to current_rssi Alberto Merciai
2021-11-19 6:38 ` Greg KH
2021-11-19 13:36 ` Alberto Merciai
2021-11-19 14:17 ` Greg KH
2021-11-19 8:51 ` Dan Carpenter
2021-11-19 12:23 ` Alberto Merciai
2021-11-19 12:29 ` Greg KH
2021-11-19 18:51 ` Your Name [this message]
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=20211119185141.GA396725@bulldog \
--to=alb3rt0.m3rciai@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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