From: Greg KH <gregkh@linuxfoundation.org>
To: Ramesh Basukala <basukalaramesh@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/01] Drivers: Fixes coding style warning
Date: Fri, 20 Jun 2014 13:40:03 -0700 [thread overview]
Message-ID: <20140620204003.GB16973@kroah.com> (raw)
In-Reply-To: <53A498B2.1000808@gmail.com>
On Fri, Jun 20, 2014 at 04:25:22PM -0400, Ramesh Basukala wrote:
> *
What is that for?
>
> From: Ramesh Basukala <basukalaramesh@gmail.com>
>
>
> Attached is a patch which fixes coding style warning message while running
> checkpatch script.
>
>
> This patch is currently against a linux 3.15.0-rc15-next kernel. I am
There is no 3.15-rc15 kernel release :(
> submitting this patch as a part of Eudyptula Challenge task.
Not needed here.
>
>
> Signed-off-by: Ramesh Basukala <basukalaramesh@gmail.com>
> *---
> Signed-off-by: Ramesh Basukala <basukalaramesh@gmail.com>
> --- xlr_net.c.original 2014-06-20 15:32:10.069732488 -0400
> +++ xlr_net.c 2014-06-20 15:35:06.841105038 -0400
> @@ -1105,6 +1105,7 @@ err_gmac:
> static int xlr_net_remove(struct platform_device *pdev)
> {
> struct xlr_net_priv *priv = platform_get_drvdata(pdev);
> +
> unregister_netdev(priv->ndev);
> mdiobus_unregister(priv->mii_bus);
> mdiobus_free(priv->mii_bus);
> **
This doesn't apply at all, please always test your patches yourself
before resending them.
Also, be explicit as to what you are fixing (what part of the kernel),
and use the scripts/get_maintainers.pl tool to send the patches to the
correct people and mailing list.
Care to try again?
greg k-h
next prev parent reply other threads:[~2014-06-20 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 20:25 [PATCH 01/01] Drivers: Fixes coding style warning Ramesh Basukala
2014-06-20 20:40 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-20 20:36 Ramesh Basukala
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=20140620204003.GB16973@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=basukalaramesh@gmail.com \
--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