All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <stefan.wahren@i2se.com>, <nsaenzju@redhat.com>,
	<cmirabil@redhat.com>, <miguel.ojeda.sandonis@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <serge@raspberrypi.org>,
	<mbrugger@suse.com>, <linux-rpi-kernel@lists.infradead.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<fedora-rpi@googlegroups.com>, <dbauman@redhat.com>,
	<mguma@redhat.com>, <jsavitz@redhat.com>
Subject: Re: [PATCH v9 0/6] Raspberry Pi Sense HAT driver
Date: Tue, 26 Apr 2022 12:03:26 +0000	[thread overview]
Message-ID: <60c3e7e4-6406-ecaa-e89b-fc2d359d8d31@microchip.com> (raw)
In-Reply-To: <4719fce9-4235-f1d7-f95e-67e5a47a0968@i2se.com>

On 26/04/2022 12:48, Stefan Wahren wrote:
> Am 26.04.22 um 12:18 schrieb Nicolas Saenz Julienne:
>> Hi Charles, Miguel,
>>
>> On Mon, 2022-04-25 at 19:34 -0400, Charles Mirabile wrote:
>>> Hi Miguel—
>>>
>>> Thanks for your help in reviewing this patch. I think all of the feedback is cleared up.
>>>
>>> I am not sure which tree this should go into, but maybe the Raspberry Pi tree maintained
>>> by Nicolas Saenz Julienne (git://git.kernel.org/pub/scm/linux/kernel/git/nsaenz/linux-
>>> rpi.git)? What do you think? Thanks!
>> Since there is no code dependency between the different drivers/patches I
>> suggest for each patch to go through its respective maintainer tree. Also, if
>> we were to move the whole series through as single tree, it's important to have
>> ACKs from all the subsystem maintainers.
> Yes, we still need a Ack of Rob for the device tree bindings. Please give him the common 2 weeks for a review.

You have one from Krzysztof on the bindings, that should be sufficient?

https://docs.kernel.org/process/maintainers.html#open-firmware-and-flattened-device-tree-bindings

>>
>> I'll do a last review during the week.
>>
>> Regards,
>>

WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <stefan.wahren@i2se.com>, <nsaenzju@redhat.com>,
	<cmirabil@redhat.com>, <miguel.ojeda.sandonis@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <serge@raspberrypi.org>,
	<mbrugger@suse.com>, <linux-rpi-kernel@lists.infradead.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<fedora-rpi@googlegroups.com>, <dbauman@redhat.com>,
	<mguma@redhat.com>, <jsavitz@redhat.com>
Subject: Re: [PATCH v9 0/6] Raspberry Pi Sense HAT driver
Date: Tue, 26 Apr 2022 12:03:26 +0000	[thread overview]
Message-ID: <60c3e7e4-6406-ecaa-e89b-fc2d359d8d31@microchip.com> (raw)
In-Reply-To: <4719fce9-4235-f1d7-f95e-67e5a47a0968@i2se.com>

On 26/04/2022 12:48, Stefan Wahren wrote:
> Am 26.04.22 um 12:18 schrieb Nicolas Saenz Julienne:
>> Hi Charles, Miguel,
>>
>> On Mon, 2022-04-25 at 19:34 -0400, Charles Mirabile wrote:
>>> Hi Miguel—
>>>
>>> Thanks for your help in reviewing this patch. I think all of the feedback is cleared up.
>>>
>>> I am not sure which tree this should go into, but maybe the Raspberry Pi tree maintained
>>> by Nicolas Saenz Julienne (git://git.kernel.org/pub/scm/linux/kernel/git/nsaenz/linux-
>>> rpi.git)? What do you think? Thanks!
>> Since there is no code dependency between the different drivers/patches I
>> suggest for each patch to go through its respective maintainer tree. Also, if
>> we were to move the whole series through as single tree, it's important to have
>> ACKs from all the subsystem maintainers.
> Yes, we still need a Ack of Rob for the device tree bindings. Please give him the common 2 weeks for a review.

You have one from Krzysztof on the bindings, that should be sufficient?

https://docs.kernel.org/process/maintainers.html#open-firmware-and-flattened-device-tree-bindings

>>
>> I'll do a last review during the week.
>>
>> Regards,
>>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-04-26 12:03 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 20:51 [PATCH v9 0/6] Raspberry Pi Sense HAT driver Charles Mirabile
2022-04-19 20:51 ` Charles Mirabile
2022-04-19 20:51 ` [PATCH v9 1/6] drivers/mfd: sensehat: Add Raspberry Pi Sense HAT to simple_mfd_i2c Charles Mirabile
2022-04-19 20:51   ` Charles Mirabile
2022-04-19 20:51 ` [PATCH v9 2/6] drivers/input/joystick: sensehat: Raspberry Pi Sense HAT joystick driver Charles Mirabile
2022-04-19 20:51   ` Charles Mirabile
2022-05-31  1:26   ` Randy Dunlap
2022-05-31  1:26     ` Randy Dunlap
2022-05-31  1:57     ` Dmitry Torokhov
2022-05-31  1:57       ` Dmitry Torokhov
2022-05-31  2:14       ` Randy Dunlap
2022-05-31  2:14         ` Randy Dunlap
2022-04-19 20:51 ` [PATCH v9 3/6] drivers/auxdisplay: sensehat: Raspberry Pi Sense HAT display driver Charles Mirabile
2022-04-19 20:51   ` Charles Mirabile
2022-05-04 17:22   ` Pavel Machek
2022-05-04 17:22     ` Pavel Machek
2022-04-19 20:51 ` [PATCH v9 4/6] dt-bindings: mfd: sensehat: Add Raspberry Pi Sense HAT schema Charles Mirabile
2022-04-19 20:51   ` Charles Mirabile
2022-04-20  6:44   ` Krzysztof Kozlowski
2022-04-20  6:44     ` Krzysztof Kozlowski
2022-04-19 20:51 ` [PATCH v9 5/6] MAINTAINERS: Add sensehat driver authors to MAINTAINERS Charles Mirabile
2022-04-19 20:51   ` Charles Mirabile
2022-04-19 20:51 ` [PATCH v9 6/6] DO NOT MERGE: full sensehat device tree overlay for raspberry pi 4 Charles Mirabile
2022-04-19 20:51   ` Charles Mirabile
2022-04-22 14:17 ` [PATCH v9 0/6] Raspberry Pi Sense HAT driver Miguel Ojeda
2022-04-22 14:17   ` Miguel Ojeda
     [not found]   ` <CABe3_aE-nQzZazLfxk1OnCNRF0sDqcWi6gieYSf4O4aYS_Ahog@mail.gmail.com>
2022-04-26 10:18     ` Nicolas Saenz Julienne
2022-04-26 10:18       ` Nicolas Saenz Julienne
2022-04-26 11:48       ` Stefan Wahren
2022-04-26 11:48         ` Stefan Wahren
2022-04-26 12:03         ` Conor.Dooley [this message]
2022-04-26 12:03           ` Conor.Dooley
2022-04-26 15:12           ` Stefan Wahren
2022-04-26 15:12             ` Stefan Wahren
2022-06-23  5:48 ` Stefan Wahren
2022-06-23  5:48   ` Stefan Wahren

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=60c3e7e4-6406-ecaa-e89b-fc2d359d8d31@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=cmirabil@redhat.com \
    --cc=dbauman@redhat.com \
    --cc=fedora-rpi@googlegroups.com \
    --cc=jsavitz@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=mbrugger@suse.com \
    --cc=mguma@redhat.com \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=nsaenzju@redhat.com \
    --cc=serge@raspberrypi.org \
    --cc=stefan.wahren@i2se.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.