From: Greg KH <greg@kroah.com>
To: Zoeb Mithaiwala <zoebm@google.com>
Cc: dan.carpenter@oracle.com, trivial@kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v3 3/3] Staging: rtl8712: Fixes a camel case variable name style issue
Date: Thu, 25 Nov 2021 18:14:36 +0100 [thread overview]
Message-ID: <YZ/EfPYxpsXg/gSm@kroah.com> (raw)
In-Reply-To: <CANMHzA4U-qc3mqz5XV4YOex-=CtsJ1UA2Xv4VaEQsf66Qfnh7g@mail.gmail.com>
On Thu, Nov 25, 2021 at 10:37:37PM +0530, Zoeb Mithaiwala wrote:
> > Where are patches 1/3 and 2/3 of this series?
> Apologies, I was unaware that the preferred method is a single email containing
> all the patches instead of a reply on the thread with only a single
> latest patch.
No one could work with a reply thread like that, right? Would you want
to review patches sent that way? :)
> > And this looks like it does not apply to any tree at all, are you sure
> you made it against the correct kernel branch? If so, what one?
> This was against torvalds/linux, but I just saw that
> https://kernelnewbies.org/FirstKernelPatch suggests using gregkh/staging,
> I will clone and make further changes on that.
Wonderful, good luck!
greg k-h
next prev parent reply other threads:[~2021-11-25 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 8:06 [PATCH] Staging: rtl8712: rtl871x_security: fixed a camel case variable name coding style issue Zoeb Mithaiwala
2021-11-20 8:26 ` Greg KH
2021-11-20 11:11 ` [PATCH 2/2] " Zoeb Mithaiwala
2021-11-22 10:39 ` Dan Carpenter
2021-11-22 17:03 ` [PATCH v3 3/3] Staging: rtl8712: Fixes a camel case variable name " Zoeb Mithaiwala
2021-11-24 10:01 ` Greg KH
2021-11-25 17:07 ` Zoeb Mithaiwala
2021-11-25 17:14 ` Greg KH [this message]
2021-11-24 10:00 ` [PATCH 2/2] Staging: rtl8712: rtl871x_security: fixed a camel case variable name coding " Greg KH
2021-11-22 15:22 ` [PATCH] " kernel test robot
2021-11-26 8:54 ` kernel test robot
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=YZ/EfPYxpsXg/gSm@kroah.com \
--to=greg@kroah.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=trivial@kernel.org \
--cc=zoebm@google.com \
/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).