All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Douglas Miller <dougmill@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: xmon memory dump does not handle LE
Date: Tue, 07 Feb 2017 12:00:06 +1100	[thread overview]
Message-ID: <87r33ag6i1.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <4efc7afd-647c-106d-ca90-5f736514f5fc@linux.vnet.ibm.com>

Douglas Miller <dougmill@linux.vnet.ibm.com> writes:

> Hi Michael,
>
> Yes, your patch seems a more complete solution. The idea of "d1", "d2", 
> "d4", and "d8" commands is more what I needed and makes more sense to 
> someone hitting xmon "cold". I'll work on getting your patch submitted.
>
>
> Question on these sorts of patches (PPC only), do we submit initially to 
> upstream, or here on this (PPC) mailing list?

Yeah send them here. Patches that are only touch powerpc should come
here, from where I merge them and then send them to Linus.

Anything that touches powerpc and some other code should at least be
CC'ed here.

If you're ever in doubt where to send a patch you can use:

  $ ./scripts/get_maintainer.pl --nogit-fallback --no-rolestats -f arch/powerpc/xmon/xmon.c
  Benjamin Herrenschmidt <benh@kernel.crashing.org>
  Paul Mackerras <paulus@samba.org>
  Michael Ellerman <mpe@ellerman.id.au>
  linuxppc-dev@lists.ozlabs.org
  linux-kernel@vger.kernel.org

> It would be nice to get this into the distros as soon as possible.

This isn't a bug fix so the distros won't pick it up automatically.
You'll have to ask them specifically to take a backport.


cheers

      parent reply	other threads:[~2017-02-07  1:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 14:42 xmon memory dump does not handle LE Douglas Miller
2017-02-03  1:46 ` Michael Ellerman
2017-02-03  3:07   ` Douglas Miller
2017-02-03 10:31     ` Michael Ellerman
2017-02-06 13:50       ` Douglas Miller
2017-02-06 20:37         ` Douglas Miller
2017-02-07  1:00         ` Michael Ellerman [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=87r33ag6i1.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=dougmill@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.