From: Greg KH <gregkh@linuxfoundation.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
sboyd@kernel.org, rafael@kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH] devcoredump : Serialize devcd_del work
Date: Fri, 22 Apr 2022 15:55:48 +0200 [thread overview]
Message-ID: <YmKz5OzW5IgJnX0r@kroah.com> (raw)
In-Reply-To: <YmKb+xWkfNGiYBHD@kroah.com>
On Fri, Apr 22, 2022 at 02:13:47PM +0200, Greg KH wrote:
>
> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> 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 22, 2022 at 03:33:08PM +0530, Mukesh Ojha wrote:
> >
> > Hi All,
> >
> > Request you all the review comments on the fix of the described problem?
> >
> > -Mukesh
> >
> >
> > On 4/19/2022 3:57 PM, Mukesh Ojha wrote:
>
> You sent this 3 days ago, please be realistic.
>
> If you are concerned about the delay in patch reviews, please help us
> out and review patches sent to the list. Otherwise, don't start to
> worry until at least after 2 weeks.
You also didn't even cc: me, so how could I see this at all?
So, nothing to review in my inbox, nice!
{sigh}
next prev parent reply other threads:[~2022-04-22 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 10:27 Mukesh Ojha
2022-04-22 10:03 ` Mukesh Ojha
2022-04-22 12:13 ` Greg KH
2022-04-22 13:55 ` Greg KH [this message]
2022-04-22 13:41 ` Johannes Berg
2022-04-22 13:53 ` Johannes Berg
2022-04-22 15:21 ` Thomas Gleixner
2022-04-25 13:17 ` Mukesh Ojha
2022-05-02 15:34 Mukesh Ojha
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=YmKz5OzW5IgJnX0r@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mojha@quicinc.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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®