Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: James Hogan <james.hogan@imgtec.com>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	linux-mips@linux-mips.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/6] Documentation/sysrq.txt: Mention MIPS TLB dump (x)
Date: Mon, 20 Jul 2015 00:35:07 -0600	[thread overview]
Message-ID: <20150720003507.78e90809@lwn.net> (raw)
In-Reply-To: <20150720062511.GA16627@linux-mips.org>

On Mon, 20 Jul 2015 08:25:11 +0200
Ralf Baechle <ralf@linux-mips.org> wrote:

> ok to funnel this through the MIPS tree?

Yes, of course; I don't ever want to get in the way of docs updates
coming via other paths.  Feel free to add my Acked-by if you want.

Thanks,

jon

  reply	other threads:[~2015-07-20  6:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 15:17 [PATCH 0/6] MIPS: dump_tlb cleanups James Hogan
2015-07-15 15:17 ` James Hogan
2015-07-15 15:17 ` [PATCH 1/6] Documentation/sysrq.txt: Mention MIPS TLB dump (x) James Hogan
2015-07-15 15:17   ` James Hogan
2015-07-20  6:25   ` Ralf Baechle
2015-07-20  6:35     ` Jonathan Corbet [this message]
2015-07-15 15:17 ` [PATCH 2/6] MIPS: Refactor dumping of TLB registers for r3k/r4k James Hogan
2015-07-15 15:17   ` James Hogan
2015-07-15 15:17 ` [PATCH 3/6] MIPS: Probe for small (1KiB) page support James Hogan
2015-07-15 15:17   ` James Hogan
2015-07-15 15:17 ` [PATCH 4/6] MIPS: dump_tlb: Only dump PageGrain if interesting James Hogan
2015-07-15 15:17   ` James Hogan
2015-07-15 15:17 ` [PATCH 5/6] MIPS: dump_tlb: Dump FrameMask register if exists James Hogan
2015-07-15 15:17   ` James Hogan
2015-07-15 15:17 ` [PATCH 6/6] MIPS: Rearrange ENTRYLO field definitions James Hogan
2015-07-15 15:17   ` James Hogan

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=20150720003507.78e90809@lwn.net \
    --to=corbet@lwn.net \
    --cc=james.hogan@imgtec.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox