From: Chandra Annamaneni <chandra627@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Chandra Annamaneni <chandra627@gmail.com>,
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: Fri, 21 Apr 2017 11:06:54 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1704211105520.25241@panther> (raw)
In-Reply-To: <20170421084057.GA31357@kroah.com>
Sorry about the top posting.
I did ask about it on the 9th of April and the reply was that the email
was 'acked'. Since I did not get a further email, I assumed it was lost.
Perhaps I misunderstood.
Thanks!
Chandra
On Fri, 21 Apr 2017, Greg KH wrote:
>
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
>
> http://daringfireball.net/2007/07/on_top
>
> On Fri, Apr 21, 2017 at 12:40:25AM -0700, Chandra Annamaneni wrote:
> >
> > Third Reminder. Please review.
>
> 2 days after you asked before?
>
> And I don't even see this patch in my queue, are you sure it hasn't
> already been handled, or merged, or rejected?
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2017-04-21 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 19:49 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 [this message]
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
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=alpine.DEB.2.20.1704211105520.25241@panther \
--to=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
all inboxes | Powered by JetHome®