lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
 <BL0PR11MB2913ECAA6F0C97E342F7DE22E7F42@BL0PR11MB2913.namprd11.prod.outlook.com>
Date: Tue, 4 Feb 2025 14:55:51 +0000
From: <Woojung.Huh@...rochip.com>
To: <kuba@...nel.org>
CC: <frieder.schrempf@...tron.de>, <lukma@...x.de>, <andrew@...n.ch>,
	<netdev@...r.kernel.org>, <Tristram.Ha@...rochip.com>
Subject: RE: KSZ9477 HSR Offloading

Hi Jakub,

> -----Original Message-----
> From: Jakub Kicinski <kuba@...nel.org>
> Sent: Monday, February 3, 2025 6:04 PM
> To: Woojung Huh - C21699 <Woojung.Huh@...rochip.com>
> Cc: frieder.schrempf@...tron.de; lukma@...x.de; andrew@...n.ch;
> netdev@...r.kernel.org; Tristram Ha - C24268 <Tristram.Ha@...rochip.com>
> Subject: Re: KSZ9477 HSR Offloading
> 
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
> 
> On Mon, 3 Feb 2025 14:58:12 +0000 Woojung.Huh@...rochip.com wrote:
> > Hi Lukasz & Frieder,
> >
> > Oops! My bad. I confused that Lukasz was filed a case originally. Monday
> brain-freeze. :(
> >
> > Yes, it is not a public link and per-user case. So, only Frieder can see
> it.
> > It may be able for you when Frieder adds you as a team. (Not tested
> personally though)
> 
> Woojung Huh, please make sure the mailing list is informed about
> the outcomes. Taking discussion off list to a closed ticketing
> system is against community rules. See below, thanks.
> 
> Quoting documentation:
> 
>   Open development
>   ----------------
> 
>   Discussions about user reported issues, and development of new code
>   should be conducted in a manner typical for the larger subsystem.
>   It is common for development within a single company to be conducted
>   behind closed doors. However, development and discussions initiated
>   by community members must not be redirected from public to closed forums
>   or to private email conversations. Reasonable exceptions to this guidance
>   include discussions about security related issues.
> 
> See: https://www.kernel.org/doc/html/next/maintainer/feature-and-driver-
> maintainers.html#open-development

Learn new thing today. Didn't know this. Definitely I will share it
when this work is done. My intention was for easier work for request than
having me as an middleman for the issue.

Best regards,
Woojung

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ