public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	prasanna@in.ibm.com
Subject: Re: [PATCH]Kprobes IA64 - Fix race when break hits and kprobe not found
Date: Wed, 13 Jul 2005 03:56:21 +0000	[thread overview]
Message-ID: <20050712205620.A9292@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050712190231.789da83c.akpm@osdl.org>; from akpm@osdl.org on Tue, Jul 12, 2005 at 07:02:31PM -0700

On Tue, Jul 12, 2005 at 07:02:31PM -0700, Andrew Morton wrote:
> Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com> wrote:
> >
> > This patch applies on top of  "Prasanna S Panchamukhi's" recent postings
> >  Kprobes: Prevent possible race condition ia64 changes
> 
> I am not aware of such a patch.  Your patch hit a reject when I tried to
> apply it to Linus's tree.  So I don't know what's going on..

Andrew,
	I thought you might have applied http://marc.theaimsgroup.com/?l=linux-kernel&m\x112082142008250&w=2 hence I generated my patch on top of this.

No problem, I will generate this patch against Linus's tree (as this does not really depend on any other patches) and submit it again in couple of hours. 
Let me know if this is okay.

-thanks,
-Anil

  reply	other threads:[~2005-07-13  3:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13  1:52 [PATCH]Kprobes IA64 - Fix race when break hits and kprobe not found Keshavamurthy Anil S
2005-07-13  2:02 ` [PATCH]Kprobes IA64 - Fix race when break hits and kprobe not Andrew Morton
2005-07-13  3:56   ` Keshavamurthy Anil S [this message]
2005-07-13  4:51   ` [PATCH]Kprobes IA64 - Fix race when break hits and kprobe not found Keshavamurthy Anil S

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=20050712205620.A9292@unix-os.sc.intel.com \
    --to=anil.s.keshavamurthy@intel.com \
    --cc=akpm@osdl.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prasanna@in.ibm.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