From: Joe Perches <joe@perches.com>
To: Chandra Annamaneni <chandra627@gmail.com>, Greg KH <greg@kroah.com>
Cc: devel@driverdev.osuosl.org, christian.gromm@microchip.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Staging: most: use __func__ instead of the function name
Date: Tue, 25 Apr 2017 19:55:34 -0700 [thread overview]
Message-ID: <1493175334.18659.17.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1704251903400.15434@panther>
On Tue, 2017-04-25 at 19:28 -0700, Chandra Annamaneni wrote:
> I assumed the email should be a reply to the previous email so it appears
> in the thread. As to the leading spaces, it was a problem with my mail
> client.
>
> Ill resend the patch.
Did you read my suggestion to just delete these lines instead?
> --
> Chandra
>
>
> On Tue, 25 Apr 2017, Greg KH wrote:
>
> > On Mon, Apr 24, 2017 at 11:20:22PM -0700, Chandra Annamaneni wrote:
> > >
> > > Change video.c to use %s, __func__ instead of function names.
> > > Warnings flagged by checkpatch.pl
> > >
> > > Signed-off-by: Chandra Annamaneni <chandra627@gmail.com>
> >
> > Why is this indented? Why is your subject a "Re:"?
> >
> >
next prev parent reply other threads:[~2017-04-26 2:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 19:49 [PATCH v3] Staging: most: use __func__ instead of the function name Chandra Annamaneni
[not found] ` <CAEge-i4Y9jfLjRg5pBB7vMcwLKUgPLwfvOCd65yc4_z4pp_nsQ@mail.gmail.com>
2017-04-10 11:21 ` Christian Gromm
2017-04-21 7:40 ` Chandra Annamaneni
2017-04-21 8:40 ` Greg KH
2017-04-21 18:06 ` Chandra Annamaneni
2017-04-21 18:19 ` Greg KH
2017-04-25 6:20 ` Chandra Annamaneni
2017-04-25 18:36 ` Greg KH
2017-04-26 2:28 ` Chandra Annamaneni
2017-04-26 2:55 ` Joe Perches [this message]
2017-04-21 10:30 ` Joe Perches
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=1493175334.18659.17.camel@perches.com \
--to=joe@perches.com \
--cc=chandra627@gmail.com \
--cc=christian.gromm@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.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