All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	dri-devel@lists.freedesktop.org,
	Steven Price <steven.price@arm.com>,
	kernel@collabora.com, Ezequiel Garcia <ezequiel@collabora.com>
Subject: Re: [PATCH] drm/panfrost: Prefix interrupt handlers' names
Date: Fri, 13 Dec 2019 15:31:45 +0000	[thread overview]
Message-ID: <b44f31b3-ff81-1b41-e25c-cb424f990606@arm.com> (raw)
In-Reply-To: <20191213143225.GB3640@kevin>

On 13/12/2019 2:32 pm, Alyssa Rosenzweig wrote:
>> TBH it would probably be sufficient to save the bother of allocating
>> strings and just settle on "panfrost-{gpu,job,mmu}", since upstream
>> users are unlikely to ever come across a system with more than one
>> Mali in it ;)
> 
> Agreed.
> 
> ----Wait, you said *upstream*? Are there .... oh no

Heh, fear not - I'm only thinking of the "Juno board with FPGA 
prototyping stack" setup, and the people using those in anger are all 
working on some other driver anyway ;)

Robin.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-12-13 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 12:39 [PATCH] drm/panfrost: Prefix interrupt handlers' names Ezequiel Garcia
2019-12-13 13:18 ` Neil Armstrong
2019-12-13 13:46   ` Robin Murphy
2019-12-13 14:32     ` Alyssa Rosenzweig
2019-12-13 15:31       ` Robin Murphy [this message]
2019-12-13 15:49         ` Alyssa Rosenzweig
2019-12-13 15:46     ` Ezequiel Garcia
2019-12-13 15:51       ` Alyssa Rosenzweig

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=b44f31b3-ff81-1b41-e25c-cb424f990606@arm.com \
    --to=robin.murphy@arm.com \
    --cc=alyssa.rosenzweig@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ezequiel@collabora.com \
    --cc=kernel@collabora.com \
    --cc=narmstrong@baylibre.com \
    --cc=steven.price@arm.com \
    --cc=tomeu.vizoso@collabora.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 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.