devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Conor.Dooley@microchip.com
Cc: conor@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, Daire.McNamara@microchip.com,
	linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: rtc: mpfs-rtc: remove Lewis from maintainers
Date: Fri, 11 Oct 2024 14:30:36 +0200	[thread overview]
Message-ID: <202410111230367324262a@mail.local> (raw)
In-Reply-To: <c565f64b-9d5b-4dee-945d-44be9762282e@microchip.com>

Hello,

On 11/10/2024 11:00:40+0000, Conor.Dooley@microchip.com wrote:
> On 11/10/2024 11:39, Conor Dooley wrote:
> > Lewis hasn't worked at Microchip for a while, and IIRC never actually
> > worked on the RTC in the first place. Remove him from the maintainers
> > list in the binding, leaving Daire.
> > 
> > Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> > ---
> > Noticed him in the CC list of your rename, figured it was worth removing
> > him, even though I don't /think/ our mail system will create bounce spam
> > in this case.
> 

I never received this patch and lore seems to agree with me:

https://lore.kernel.org/all/c565f64b-9d5b-4dee-945d-44be9762282e@microchip.com/

[parent not found: <20241011-boozy-blinking-f76d3891dacd@wendy>]

Can you resend?

> I was wrong, it does generate bounce spam :/
> 

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2024-10-11 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241011-boozy-blinking-f76d3891dacd@wendy>
2024-10-11 11:00 ` [PATCH] dt-bindings: rtc: mpfs-rtc: remove Lewis from maintainers Conor.Dooley
2024-10-11 12:30   ` Alexandre Belloni [this message]
2024-10-11 14:45     ` Conor Dooley

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=202410111230367324262a@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=Conor.Dooley@microchip.com \
    --cc=Daire.McNamara@microchip.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).