From: Greg KH <gregkh@linuxfoundation.org>
To: Atul Gopinathan <leoatul12@gmail.com>
Cc: mchehab+huawei@kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: hikey9xx: fix checkpatch error and warning
Date: Tue, 9 Feb 2021 07:08:53 +0100 [thread overview]
Message-ID: <YCIm9e0w06aeOL91@kroah.com> (raw)
In-Reply-To: <20210209055703.7211-1-leoatul12@gmail.com>
On Tue, Feb 09, 2021 at 11:27:04AM +0530, Atul Gopinathan wrote:
> Fix the following types of checkpatch error and warning:
>
> ERROR: code indent should use tabs where possible
> WARNING: struct phy_ops should normally be const
That is 2 different things, which means this should be 2 different
patches. Please make this a patch series and resend.
thanks,
greg k-h
prev parent reply other threads:[~2021-02-09 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 5:57 [PATCH] staging: hikey9xx: fix checkpatch error and warning Atul Gopinathan
2021-02-09 6:08 ` Greg KH [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=YCIm9e0w06aeOL91@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=leoatul12@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@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