linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Finn Thain <fthain@telegraphics.com.au>,
	geert@linux-m68k.org
Cc: linux-m68k@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 00/12] macintosh: Resolve various PMU driver problems
Date: Wed, 27 Jun 2018 17:39:15 +1200	[thread overview]
Message-ID: <5d4d7ca4-1d2f-268f-e5d2-eddb213e894d@gmail.com> (raw)
In-Reply-To: <cacaecac00c1ac941a78da772bbcfb05142df87d.camel@kernel.crashing.org>

Ben,

Am 27.06.2018 um 15:27 schrieb Benjamin Herrenschmidt:
> On Wed, 2018-06-27 at 13:08 +1000, Michael Ellerman wrote:
>>> I will rewrite patch 10/12 after Arnd's fixes and this series have all
>>> made their way through both powerpc and m68k trees, and submit it
>>> separately.
>>
>> drivers/macintosh is supposedly maintained by Ben, but I'm not sure this
>> series is high on his todo list.
>
> We need at least to pull out a couple of powerbooks we have sitting in
> drawers and try it out.

No need to root around in drawers - I'm sitting in front of one (G3 
Titanium) writing this. Let me know if that would help (I've forgotten 
most of what I knew about powerpc kernels).

Cheers,

	Michael


>
>>
>> Should it just go in via the m68k tree?
>>
>> Or I can create a topic branch to share it between ppc and m68k?

  reply	other threads:[~2018-06-27  5:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1528885172.git.fthain@telegraphics.com.au>
     [not found] ` <alpine.LNX.2.21.1806242119180.34@nippy.intranet>
     [not found]   ` <874lhp6i4d.fsf@concordia.ellerman.id.au>
2018-06-27  3:27     ` [PATCH v3 00/12] macintosh: Resolve various PMU driver problems Benjamin Herrenschmidt
2018-06-27  5:39       ` Michael Schmitz [this message]
2018-06-27  9:00         ` Gabriel Paubert
2018-06-27  9:14           ` Michael Schmitz

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=5d4d7ca4-1d2f-268f-e5d2-eddb213e894d@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=fthain@telegraphics.com.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).