From: David Miller <davem@davemloft.net>
To: ahiliation@yahoo.co.in
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1]net:ethernet:fixed a coding style issue relating space.
Date: Sat, 19 May 2012 14:36:08 -0400 (EDT) [thread overview]
Message-ID: <20120519.143608.2217025686579966031.davem@davemloft.net> (raw)
In-Reply-To: <1337421732.6524.YahooMailNeo@web192306.mail.sg3.yahoo.com>
From: Jeffrin Jose <ahiliation@yahoo.co.in>
Date: Sat, 19 May 2012 18:02:12 +0800 (SGT)
>>> Rather than put lips on a pig, why not remove the bogus if?
> is there anything i should work on this patch or should i move on
He's telling you to remove the code rather then try to fix
it's coding style.
prev parent reply other threads:[~2012-05-19 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 21:45 [PATCH 1/1]net:ethernet:fixed a coding style issue relating space Jeffrin Jose
2012-05-18 21:56 ` Stephen Hemminger
[not found] ` <1337421732.6524.YahooMailNeo@web192306.mail.sg3.yahoo.com>
2012-05-19 18:36 ` David Miller [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=20120519.143608.2217025686579966031.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ahiliation@yahoo.co.in \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).