Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
	<intel-wired-lan@lists.osuosl.org>,
	"Lifshits, Vitaly" <vitaly.lifshits@intel.com>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [Intel-wired-lan] Expected effects of layoffs on driver Intel Wired Ethernet driver development?
Date: Thu, 7 Nov 2024 10:49:21 -0800	[thread overview]
Message-ID: <19b30532-213b-4c96-9896-391c2f83dfd7@intel.com> (raw)
In-Reply-To: <80949168-67a8-4d28-a6c7-3cae9f92daad@molgen.mpg.de>



On 11/6/2024 10:07 PM, Paul Menzel wrote:
> Dear Intel Wired Ethernet Linux Kernel driver folks,
> 
> 
> It looks like some developers are not working for Intel anymore – like 
> Sasha Neftin. I assume this is a result of layoffs from the news [1]. Is 
> this true, or was the team *not* affected by the layoffs, and developers 
> just moved on by themselves?
> 
> If it was due to layoffs, could you please share, how the team was 
> affected and how Intel is going to make sure, that driver developments 
> continues as before, so customers know what to expect?

Hi Paul,

I don't believe I can share that information. However, all our supported 
drivers will continue to be developed and supported.

For our client drivers, Vitaly can assist.

Thanks,
Tony

> Kind regards,
> 
> Paul
> 
> 
> [1]: https://www.theverge.com/2024/8/1/24210656/intel-is-laying-off- 
> over-10000-employees-and-will-cut-10-billion-in-costs
>       "Intel is laying off over 15,000 employees and will stop ‘non- 
> essential work’",  Aug 1, 2024, 10:14 PM GMT+2


  reply	other threads:[~2024-11-07 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07  6:07 [Intel-wired-lan] Expected effects of layoffs on driver Intel Wired Ethernet driver development? Paul Menzel
2024-11-07 18:49 ` Tony Nguyen [this message]
2024-11-08 11:58   ` Przemek Kitszel

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=19b30532-213b-4c96-9896-391c2f83dfd7@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=vitaly.lifshits@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