public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Avizrat, Yaron" <yaron.avizrat@intel.com>,
	Oded Gabbay <ogabbay@kernel.org>
Cc: Ofir Bitton <obitton@habana.ai>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"airlied@gmail.com" <airlied@gmail.com>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
	"jgg@nvidia.com" <jgg@nvidia.com>,
	koby.elbaz@intel.com, konstantin.sinyuk@intel.com
Subject: Re: [PATCH 1/1] MAINTAINERS: Change habanalabs maintainer
Date: Tue, 11 Mar 2025 11:00:57 +0200	[thread overview]
Message-ID: <87bju8gcvq.fsf@intel.com> (raw)
In-Reply-To: <be353276-3dce-49c1-8a35-164a33ddb9f9@intel.com>

On Tue, 11 Mar 2025, "Avizrat, Yaron" <yaron.avizrat@intel.com> wrote:
> On 07/03/2025 11:21, Oded Gabbay wrote:
>> On Thu, Mar 06, 2025 at 03:51:24PM +0200, Avizrat, Yaron wrote:
>>> On 05/03/2025 13:57, Jani Nikula wrote:
>>>> On Wed, 05 Mar 2025, "Avizrat, Yaron" <yaron.avizrat@intel.com> 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>
>>>>>> ---
>>>>>>  MAINTAINERS | 2 +-
>>>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>>>
>>>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>>>> index ed2d2dbcec81..a4b36590061e 100644
>>>>>> --- a/MAINTAINERS
>>>>>> +++ b/MAINTAINERS
>>>>>> @@ -9599,7 +9599,7 @@ S:	Maintained
>>>>>>  F:	block/partitions/efi.*
>>>>>>
>>>>>>  HABANALABS PCI DRIVER
>>>>>> -M:	Ofir Bitton <obitton@habana.ai>
>>>>>> +M:	Yaron Avizrat <yaron.avizrat@intel.com>
>>>>>>  L:	dri-devel@lists.freedesktop.org
>>>>>>  S:	Supported
>>>>>>  C:	irc://irc.oftc.net/dri-devel
>>>>> Acked-by: Yaron Avizrat <yaron.avizrat@intel.com>
>>>>>
>>>>> Apologies for the long silence — it’s been a challenging period with
>>>>> the Habanalabs-Intel merger, but we're back and ready to continue
>>>>> contributing.
>>>>>
>>>>> We'll be moving forward with our roadmap — upstreaming the latest
>>>>> HabanaLabs driver, including recent changes and full support for the
>>>>> entire GaudiX series.
>>>>>
>>>>> To support this effort, Koby Elbaz and Konstantin Sinyuk will join me
>>>>> as co-maintainers on a regular basis.
>>>> Should they be added as maintainers in the MAINTAINERS entry too?
>>>>
>>>> Are you going to pick this up and apply to the Habanalabs repo, and send
>>>> a pull request with it? Or how do you propose to proceed?
>>>>
>>>>
>>>> BR,
>>>> Jani.
>>>>
>>> Yes, in a later patch, they would be added as maintainers in the MAINTAINERS entry too.
>>> Regarding your second question, we should start with merging Ofir's initial patch.
>>> Any additional/upcoming changes will be initially merged into the official HabanaLabs repo as you mentioned above.
>>>
>>> Regards,
>>> Yaron
>>>
>> Acked-by: Oded Gabbay <ogabbay@kernel.org>
>
> Reminder: can someone pick it up, please?

I thought you picking this up in your tree and then sending a pull
request with it would be a good exercise to get started. ;)

BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2025-03-11  9:01 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 [this message]
2025-07-05  8:09             ` Lukas Wunner

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=87bju8gcvq.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --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=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