mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mukesh Ojha <mojha@codeaurora.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	Brendan Jackman <brendan.jackman@arm.com>,
	Mathieu Malaterre <malat@debian.org>,
	gkohli@codeaurora.org, neeraju@codeaurora.org
Subject: Re: [PATCH v2] cpu/hotplug: Fix cpuhp_step name for timers
Date: Mon, 30 Jul 2018 19:03:00 +0530	[thread overview]
Message-ID: <08c9986e-f774-332e-9838-462921f5486f@codeaurora.org> (raw)
In-Reply-To: <alpine.DEB.2.21.1807301411010.2518@nanos.tec.linutronix.de>



On 7/30/2018 5:49 PM, Thomas Gleixner wrote:
> Mukesh,
>
> On Thu, 26 Jul 2018, Mukesh Ojha wrote:
>
>> Hi All,
>>
>> Can i get input on this ?
> Sure.
>
>> Thanks,
>> Mukesh
>> On 7/24/2018 8:17 PM, Mukesh Ojha wrote:
> The input you get is that it's unprofessional to poke people after TWO days
> about a patch which is purely cosmetic.
>
> It's perfectly fine to send a reminder after a week for important changes
> and after two for trivial cleanups like this. You really cannot expect that
> maintainers and other developers permanentely sit there twiddling thumbs
> and wait for new mail to arrive in order to reply immediately.

Thanks for your patience and time in replying.
Will keep the patience :-)

Regards,
Mukesh

>
> Thanks,
>
> 	tglx
>


  reply	other threads:[~2018-07-30 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 14:47 Mukesh Ojha
2018-07-26 11:52 ` Mukesh Ojha
2018-07-30 12:19   ` Thomas Gleixner
2018-07-30 13:33     ` Mukesh Ojha [this message]
2018-07-30 19:33 ` [tip:smp/hotplug] cpu/hotplug: Clarify CPU hotplug step " tip-bot for 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=08c9986e-f774-332e-9838-462921f5486f@codeaurora.org \
    --to=mojha@codeaurora.org \
    --cc=brendan.jackman@arm.com \
    --cc=gkohli@codeaurora.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malat@debian.org \
    --cc=mingo@kernel.org \
    --cc=neeraju@codeaurora.org \
    --cc=peterz@infradead.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
Powered by JetHome