All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <palmer@dabbelt.com>, <arnd@arndb.de>
Cc: <soc@kernel.org>, <Daire.McNamara@microchip.com>,
	<broonie@kernel.org>, <wsa@kernel.org>,
	<thierry.reding@gmail.com>, <u.kleine-koenig@pengutronix.de>,
	<jassisinghbrar@gmail.com>, <linus.walleij@linaro.org>,
	<brgl@bgdev.pl>, <gregkh@linuxfoundation.org>, <olof@lixom.net>,
	<mturquette@baylibre.com>, <sboyd@kernel.org>,
	<devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: [RESEND/PULL PATCH 0/2] MAINTAINERS updates for PolarFire SoC
Date: Fri, 26 Aug 2022 06:22:07 +0000	[thread overview]
Message-ID: <196dcae3-542a-2cf3-ebee-e7ecc4a8a330@microchip.com> (raw)
In-Reply-To: <mhng-9fab66cf-3d6c-417b-9233-8030c256aea9@palmer-mbp2014>

On 26/08/2022 01:15, Palmer Dabbelt wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Wed, 10 Aug 2022 07:02:42 PDT (-0700), conor.dooley@microchip.com wrote:
>> Hey Arnd,
>>
>> Could you please take the following two patches via the soc tree when
>> you get a chance?

> Thanks, these are on fixes.

I think these already were applied by Arnd. I guess the soc patchwork
bot does not CC the people on the original mail, only the author.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <palmer@dabbelt.com>, <arnd@arndb.de>
Cc: <soc@kernel.org>, <Daire.McNamara@microchip.com>,
	<broonie@kernel.org>, <wsa@kernel.org>,
	<thierry.reding@gmail.com>, <u.kleine-koenig@pengutronix.de>,
	<jassisinghbrar@gmail.com>, <linus.walleij@linaro.org>,
	<brgl@bgdev.pl>, <gregkh@linuxfoundation.org>, <olof@lixom.net>,
	<mturquette@baylibre.com>, <sboyd@kernel.org>,
	<devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: [RESEND/PULL PATCH 0/2] MAINTAINERS updates for PolarFire SoC
Date: Fri, 26 Aug 2022 06:22:07 +0000	[thread overview]
Message-ID: <196dcae3-542a-2cf3-ebee-e7ecc4a8a330@microchip.com> (raw)
In-Reply-To: <mhng-9fab66cf-3d6c-417b-9233-8030c256aea9@palmer-mbp2014>

On 26/08/2022 01:15, Palmer Dabbelt wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Wed, 10 Aug 2022 07:02:42 PDT (-0700), conor.dooley@microchip.com wrote:
>> Hey Arnd,
>>
>> Could you please take the following two patches via the soc tree when
>> you get a chance?

> Thanks, these are on fixes.

I think these already were applied by Arnd. I guess the soc patchwork
bot does not CC the people on the original mail, only the author.

  reply	other threads:[~2022-08-26  6:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 14:02 [RESEND/PULL PATCH 0/2] MAINTAINERS updates for PolarFire SoC Conor Dooley
2022-08-10 14:02 ` 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 [this message]
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=196dcae3-542a-2cf3-ebee-e7ecc4a8a330@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=Daire.McNamara@microchip.com \
    --cc=arnd@arndb.de \
    --cc=brgl@bgdev.pl \
    --cc=broonie@kernel.org \
    --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=palmer@dabbelt.com \
    --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.