From: Greg KH <gregkh@linuxfoundation.org>
To: Aravind Ceyardass <aravind.pub@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, devel@driverdev.osuosl.org,
valdis.kletnieks@vt.edu
Subject: Re: [PATCH] staging: exfat: Fix checkpatch.pl camelcase issues
Date: Thu, 19 Mar 2020 15:53:32 +0100 [thread overview]
Message-ID: <20200319145332.GA92193@kroah.com> (raw)
In-Reply-To: <1fed9204-59fb-8a1e-5adf-28183b3651e4@gmail.com>
On Thu, Mar 19, 2020 at 10:31:05AM -0400, Aravind Ceyardass wrote:
>
>
> On 3/19/20 10:12 AM, Greg KH wrote:
> > On Thu, Mar 19, 2020 at 10:06:47AM -0400, Aravind Ceyardass wrote:
> >> Fix ffsCamelCase function names and mixed case enums
> >>
> >> Signed-off-by: Aravind Ceyardass <aravind.pub@gmail.com>
> >> ---
> >> drivers/staging/exfat/TODO | 1 -
> >> drivers/staging/exfat/exfat.h | 12 +-
> >> drivers/staging/exfat/exfat_super.c | 222 ++++++++++++++--------------
> >> 3 files changed, 117 insertions(+), 118 deletions(-)
> >
> > These files are not in linux-next, or in my tree, anymore.
> >
> > Please always work against the latest development tree so you do not
> > waste duplicated effort.
> >
> > thanks,
> >
> > greg k-h
> >
>
> As a very beginner, I used the staging(git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git) tree based on what I read on kernelnewbies.org
>
> What tree or branch should I use instead?
That's the correct tree, but you probably forgot to use the staging-next
branch, right?
hope this helps,
greg k-h
next prev parent reply other threads:[~2020-03-19 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 14:06 [PATCH] staging: exfat: Fix checkpatch.pl camelcase issues Aravind Ceyardass
2020-03-19 14:12 ` Greg KH
2020-03-19 14:31 ` Aravind Ceyardass
2020-03-19 14:53 ` Greg KH [this message]
2020-03-19 14:27 ` Matthew Wilcox
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=20200319145332.GA92193@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aravind.pub@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.