public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Yaron Avizrat <yaron.avizrat@intel.com>
Cc: Oded Gabbay <ogabbay@kernel.org>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Ofir Bitton <obitton@habana.ai>,
	linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
	Simona Vetter <simona@ffwll.ch>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	dri-devel@lists.freedesktop.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Koby Elbaz <koby.elbaz@intel.com>,
	Konstantin Sinyuk <konstantin.sinyuk@intel.com>
Subject: Re: [PATCH 1/1] MAINTAINERS: Change habanalabs maintainer
Date: Sat, 5 Jul 2025 10:09:55 +0200	[thread overview]
Message-ID: <aGjd01Lyn5reVAEN@wunner.de> (raw)
In-Reply-To: <be353276-3dce-49c1-8a35-164a33ddb9f9@intel.com>

On Tue, Mar 11, 2025 at 10:25:05AM +0200, Avizrat, Yaron wrote:
> On 29/07/2024 15:17, Ofir Bitton wrote:
> > I will be leaving Intel soon, Yaron Avizrat will take the role
> > of habanalabs driver maintainer.
> >
> > Signed-off-by: Ofir Bitton <obitton@habana.ai>
>
> Reminder: can someone pick it up, please?

Applied to drm-misc-fixes with Yaron's, Jani's and Oded's acks.

Please submit a follow-up change to add Koby and Konstantin as
co-maintainers.

I'm picking this up despite Jani's request that you send a
pull request because retaining outdated MAINTAINERS entries
for a *year* is untenable.

Thanks,

Lukas

      parent reply	other threads:[~2025-07-05  8:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 12:17 [PATCH 0/1] Update on habanalabs maintainer status Ofir Bitton
2024-07-29 12:17 ` [PATCH 1/1] MAINTAINERS: Change habanalabs maintainer Ofir Bitton
2025-03-05 10:48   ` Avizrat, Yaron
2025-03-05 11:57     ` Jani Nikula
2025-03-06 13:51       ` Avizrat, Yaron
2025-03-06 14:12         ` Jani Nikula
2025-03-07  9:21         ` Oded Gabbay
2025-03-11  8:25           ` Avizrat, Yaron
2025-03-11  9:00             ` Jani Nikula
2025-07-05  8:09             ` Lukas Wunner [this message]

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=aGjd01Lyn5reVAEN@wunner.de \
    --to=lukas@wunner.de \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=jgg@nvidia.com \
    --cc=koby.elbaz@intel.com \
    --cc=konstantin.sinyuk@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=obitton@habana.ai \
    --cc=ogabbay@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=simona@ffwll.ch \
    --cc=yaron.avizrat@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox