linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oren Twaig <oren@scalemp.com>
To: "H. Peter Anvin" <hpa@zytor.com>, Richard Weinberger <richard@nod.at>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	David Rientjes <rientjes@google.com>,
	Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Andi Kleen <ak@linux.intel.com>,
	HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Ping: Re: [PATCH v2] x86, vsmp: Remove is_vsmp_box() from apic_is_clustered_box()
Date: Sun, 13 Jul 2014 21:36:31 +0300	[thread overview]
Message-ID: <53C2D1AF.1090109@scalemp.com> (raw)
In-Reply-To: <6C1FDCA1-4550-45AC-A8CD-78FF8EB268BD@zytor.com>

I see - thanks.

BTW, the v2 was sent because I had a mailer send-as-text issues which caused
the patch not to be sent properly and you had some conflicts with it when
merging.

All should be good now with the v2.

Thanks,
Oren.
On 7/13/2014 7:40 PM, H. Peter Anvin wrote:
> Yes, although sometimes pings we useful to keep things from getting lost.  Typically 1-2 weeks without response is a good reason to ping.  *Don't repost*, just put a ping as a reply to the original 0/ patch, which in most threaded mail readers brings the thread back to the front.
>
> Sent from my tablet, pardon any formatting problems.
>
>> On Jul 13, 2014, at 2:10, Richard Weinberger <richard@nod.at> wrote:
>>
>> Am 13.07.2014 08:51, schrieb Oren Twaig:
>>> ping
>>> On 07/06/2014 09:33 AM, Oren Twaig wrote:
>>>> Hi,
>>>>
>>>> Quick question: As I'm new at this (submitting patches), what is a reasonable
>>>> time to wait before ping-ing a patch ?
>>>>
>>>> Oren.
>> AFACT Peter is still crawling through his mail backlog to catch up.
>>
>> Thanks,
>> //richard
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>



---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com


  reply	other threads:[~2014-07-13 18:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 10:01 [PATCH v2] x86, vsmp: Remove is_vsmp_box() from apic_is_clustered_box() Oren Twaig
2014-07-06  6:32 ` Oren Twaig
2014-07-06  6:33 ` Oren Twaig
2014-07-13  6:51   ` Ping: " Oren Twaig
2014-07-13  9:10     ` Richard Weinberger
2014-07-13  9:27       ` Oren Twaig
2014-07-13 16:40       ` H. Peter Anvin
2014-07-13 18:36         ` Oren Twaig [this message]
2014-07-14  1:55 ` [tip:x86/apic] " tip-bot for Oren Twaig
2014-08-01 22:12 ` [tip:x86/apic] x86/apic/vsmp: Make is_vsmp_box() static tip-bot for H. Peter Anvin

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=53C2D1AF.1090109@scalemp.com \
    --to=oren@scalemp.com \
    --cc=ak@linux.intel.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=hpa@zytor.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=richard@nod.at \
    --cc=rientjes@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yoshihiro.yunomae.ez@hitachi.com \
    /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).