Linux SPI subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Mathias Krause <minipli-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Cc: "Rafael J. Wysocki" <rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org>,
	Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Daniel Mack <daniel-cYrQPVfZoowdnm+yROfE0A@public.gmane.org>,
	Haojian Zhuang
	<haojian.zhuang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Robert Jarzmik <robert.jarzmik-GANU6spQydw@public.gmane.org>
Subject: Re: [PATCH] spi: spi-pxa2xx: Constify ACPI device ids
Date: Mon, 15 Jun 2015 20:14:58 +0100	[thread overview]
Message-ID: <20150615191458.GC18309@sirena.org.uk> (raw)
In-Reply-To: <CA+rthh8WEzdY0vxV-oQ7xTUCtqbhJkTUeym9VNPU+Xm6a7T=YA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

On Mon, Jun 15, 2015 at 07:47:37PM +0200, Mathias Krause wrote:

> Was that wrong? Who else should I've send the patch to? Maybe they
> should be added to the MAINTAINERS file?

I'd have expected at least Jarkko (who's been actively working on the
ACPI stuff for this driver) - in general MAINTAINERS is a bit
unreliable, you should probably glance at git log.

> Rafael and Len are on Cc because of [1] -- an effort to constify all
> users of struct acpi_device_id. They're on Cc because of the ACPI
> relation. I hope that clears it up.

Consider if every single patch adding a const to an ACPI ID list really
needs to go to the ACPI maintainers (I know I get a lot of really odd
stuff registering SPI devices).

> I was uncertain how to group those changes but tried to split them up
> per-system. So you're seeing only the patches where you are mentioned
> as a maintainer. I thought it would be less noise this way for the
> non-ACPI related patches. It's a simple patch, after all.

That bit is fine.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2015-06-15 19:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-13 12:22 [PATCH] spi: spi-pxa2xx: Constify ACPI device ids Mathias Krause
     [not found] ` <1434198134-8278-1-git-send-email-minipli-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2015-06-15  9:53   ` Mark Brown
     [not found]     ` <20150615095344.GE18309-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-06-15 17:47       ` Mathias Krause
     [not found]         ` <CA+rthh8WEzdY0vxV-oQ7xTUCtqbhJkTUeym9VNPU+Xm6a7T=YA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-15 19:14           ` Mark Brown [this message]
2015-06-15 19:12       ` Robert Jarzmik
     [not found]         ` <878ubkbxbd.fsf-4ty26DBLk+jEm7gnYqmdkQ@public.gmane.org>
2015-06-15 19:20           ` Mark Brown
     [not found]             ` <20150615192025.GE18309-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-06-16  9:37               ` Mika Westerberg

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=20150615191458.GC18309@sirena.org.uk \
    --to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=daniel-cYrQPVfZoowdnm+yROfE0A@public.gmane.org \
    --cc=haojian.zhuang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=minipli-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
    --cc=rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org \
    --cc=robert.jarzmik-GANU6spQydw@public.gmane.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