mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>
To: mhiramat@redhat.com
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	jdike@addtoit.com, tony.luck@intel.com
Subject: Re: [RFC, PATCH 0/4] elf_core_dump(): Add extended numbering support
Date: Wed, 16 Dec 2009 12:02:12 +0900 (JST)	[thread overview]
Message-ID: <20091216.120212.112622365.d.hatayama@jp.fujitsu.com> (raw)
In-Reply-To: <4B27A6BC.5080402@redhat.com>

> Hi HATAYAMA-san,
> 
> Daisuke HATAYAMA wrote:
> > Question to Maintainers
> > ========
> > 
> > I know these patches are conflicting with Hiramatsu-san's
> > (http://lkml.org/lkml/2009/11/28/143), so I am planning to remake
> > them. But now, I don't know what tree is sutable to send these
> > patches. Do you have any suggestions?
> 
> Currently, my patches are merged into Andrew's -mm tree.
> I think your patch also may be picked up to -mm tree.

I see.

So, I remake the patches for the latest -mm tree.

Thanks.

> 
> BTW, I had asked him and Ingo that is possible to copy it to
> -tip tree too, because coredump tracepoint patch depends
> on both of signal-tracepoint and the coredump parameters
> patch. However, since now signal-tracepoint patches has
> been merged to linus git tree, I assume that coredump
> tracepoint patch can be applied after -mm tree moved on
> to .33-rc1.
> 
> 
> Thank you!
> 
> -- 
> Masami Hiramatsu
> 
> Software Engineer
> Hitachi Computer Products (America), Inc.
> Software Solutions Division
> 
> e-mail: mhiramat@redhat.com
> 

      reply	other threads:[~2009-12-16  3:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15  2:40 Daisuke HATAYAMA
2009-12-15 15:09 ` Masami Hiramatsu
2009-12-16  3:02   ` Daisuke HATAYAMA [this message]

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=20091216.120212.112622365.d.hatayama@jp.fujitsu.com \
    --to=d.hatayama@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@redhat.com \
    --cc=tony.luck@intel.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

all inboxes | Powered by JetHome®