From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Conor Dooley <conor@kernel.org>
Cc: claudiu beznea <claudiu.beznea@tuxon.dev>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
soc@kernel.org
Subject: Re: microchip soc maintainance change proposal
Date: Wed, 25 Sep 2024 19:59:52 +0200 [thread overview]
Message-ID: <20240925175952d2737996@mail.local> (raw)
In-Reply-To: <20240925-absolute-jockey-1518cceb2884@spud>
On 25/09/2024 17:16:10+0100, Conor Dooley wrote:
> On Wed, Sep 25, 2024 at 10:34:10AM +0300, claudiu beznea wrote:
> >
> >
> > On 24.09.2024 17:24, Alexandre Belloni wrote:
> > > On 24/09/2024 16:05:45+0200, Nicolas Ferre wrote:
> > >> On 24/09/2024 at 13:46, Conor Dooley wrote:
> > >>> Hey folks,
> > >>>
> > >>> I mentioned this to Arnd and Alexandre at LPC, and to Nicolas before
> > >>> that, but I would like to propose some changes to how the Microchip soc
> > >>> support is maintained - mostly affecting the riscv side of things that
> > >>> I've been maintaining in my personal tree, alongside other platforms.
> > >>> I'd like to propose moving those from my tree, into the at91 tree.
> > >>
> > >> I don't know if the "at91" naming will remain a right designation of what
> > >> we're doing in the future, but well, let's stick to it for now.
> > >> Some find it a little too much tight to the old Atmel brand...
> > >>
> > >
> > > We could take this opportunity to rename the tree microchip or mchp.
> >
> > +1
>
> I personally don't care at all about the tree being called at91 or w/e,
> but I wouldn't object to a rename to either. I can whip up a mail to the
> helpdesk if yous like.
Yeah, I guess you can ask for the rename and be added to the list of
users that can push to the repo. At the same time, you can send a patch
to update the MAINTAINER entry so we can ack it.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-09-25 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 11:46 microchip soc maintainance change proposal Conor Dooley
2024-09-24 14:05 ` Nicolas Ferre
2024-09-24 14:24 ` Alexandre Belloni
2024-09-25 7:34 ` claudiu beznea
2024-09-25 16:16 ` Conor Dooley
2024-09-25 17:59 ` Alexandre Belloni [this message]
2024-09-26 17:19 ` Conor Dooley
2024-09-27 8:03 ` Nicolas Ferre
2024-09-30 16:51 ` 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=20240925175952d2737996@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=soc@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.