All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: <soc@kernel.org>, Daire McNamara <daire.mcnamara@microchip.com>
Cc: "Mark Brown" <broonie@kernel.org>,
	"Wolfram Sang" <wsa@kernel.org>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Jassi Brar" <jassisinghbrar@gmail.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Bartosz Golaszewski" <brgl@bgdev.pl>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Olof Johansson" <olof@lixom.net>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	"Conor Dooley" <conor.dooley@microchip.com>
Subject: [RESEND/PULL PATCH 0/2] MAINTAINERS updates for PolarFire SoC
Date: Wed, 10 Aug 2022 15:02:42 +0100	[thread overview]
Message-ID: <20220810140243.2685416-1-conor.dooley@microchip.com> (raw)

Hey Arnd,

Could you please take the following two patches via the soc tree when
you get a chance?

The first is adding coverage for "my" dt-bindings as suggested by Mark.
I CCed all the subsystem maintainers on a V1 a week ago & I've added
them explicity to the patch text this time as CCs. Correct me if I am
wrong, but I am operating on the assumption that their Acks are not
required here. Hopefully increasing the binding coverage is non
controversial!

The second patch is a resend of a patch that was deferred to later in
the merge window avoid messing about with a 4th conflict in the entry.

Thanks,
Conor.

Conor Dooley (2):
  MAINTAINERS: add PolarFire SoC dt bindings
  MAINTAINERS: add the Polarfire SoC's i2c driver

 MAINTAINERS | 10 ++++++++++
 1 file changed, 10 insertions(+)


base-commit: 4e23eeebb2e57f5a28b36221aa776b5a1122dde5
-- 
2.36.1


WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com>
To: <soc@kernel.org>, Daire McNamara <daire.mcnamara@microchip.com>
Cc: "Mark Brown" <broonie@kernel.org>,
	"Wolfram Sang" <wsa@kernel.org>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Jassi Brar" <jassisinghbrar@gmail.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Bartosz Golaszewski" <brgl@bgdev.pl>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Olof Johansson" <olof@lixom.net>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	"Conor Dooley" <conor.dooley@microchip.com>
Subject: [RESEND/PULL PATCH 0/2] MAINTAINERS updates for PolarFire SoC
Date: Wed, 10 Aug 2022 15:02:42 +0100	[thread overview]
Message-ID: <20220810140243.2685416-1-conor.dooley@microchip.com> (raw)

Hey Arnd,

Could you please take the following two patches via the soc tree when
you get a chance?

The first is adding coverage for "my" dt-bindings as suggested by Mark.
I CCed all the subsystem maintainers on a V1 a week ago & I've added
them explicity to the patch text this time as CCs. Correct me if I am
wrong, but I am operating on the assumption that their Acks are not
required here. Hopefully increasing the binding coverage is non
controversial!

The second patch is a resend of a patch that was deferred to later in
the merge window avoid messing about with a 4th conflict in the entry.

Thanks,
Conor.

Conor Dooley (2):
  MAINTAINERS: add PolarFire SoC dt bindings
  MAINTAINERS: add the Polarfire SoC's i2c driver

 MAINTAINERS | 10 ++++++++++
 1 file changed, 10 insertions(+)


base-commit: 4e23eeebb2e57f5a28b36221aa776b5a1122dde5
-- 
2.36.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2022-08-10 14:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 14:02 Conor Dooley [this message]
2022-08-10 14:02 ` [RESEND/PULL PATCH 0/2] MAINTAINERS updates for PolarFire SoC Conor Dooley
2022-08-10 14:02 ` [RESEND PATCH 1/2] MAINTAINERS: add PolarFire SoC dt bindings Conor Dooley
2022-08-10 14:02   ` Conor Dooley
2022-08-10 17:11   ` Uwe Kleine-König
2022-08-10 17:11     ` Uwe Kleine-König
2022-08-26  0:15     ` Palmer Dabbelt
2022-08-26  0:15       ` Palmer Dabbelt
2022-08-10 14:02 ` [RESEND PATCH 2/2] MAINTAINERS: add the Polarfire SoC's i2c driver Conor Dooley
2022-08-10 14:02   ` Conor Dooley
2022-08-10 20:20 ` [RESEND/PULL PATCH 0/2] MAINTAINERS updates for PolarFire SoC patchwork-bot+linux-soc
2022-08-26  0:15 ` Palmer Dabbelt
2022-08-26  0:15   ` Palmer Dabbelt
2022-08-26  6:22   ` Conor.Dooley
2022-08-26  6:22     ` Conor.Dooley
2022-08-26 14:33     ` Palmer Dabbelt
2022-08-26 14:33       ` Palmer Dabbelt

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=20220810140243.2685416-1-conor.dooley@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=arnd@arndb.de \
    --cc=brgl@bgdev.pl \
    --cc=broonie@kernel.org \
    --cc=daire.mcnamara@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=olof@lixom.net \
    --cc=sboyd@kernel.org \
    --cc=soc@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=wsa@kernel.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 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.