From: Jakub Kicinski <kuba@kernel.org>
To: <Woojung.Huh@microchip.com>
Cc: <frieder.schrempf@kontron.de>, <lukma@denx.de>, <andrew@lunn.ch>,
<netdev@vger.kernel.org>, <Tristram.Ha@microchip.com>
Subject: Re: KSZ9477 HSR Offloading
Date: Mon, 3 Feb 2025 15:04:18 -0800 [thread overview]
Message-ID: <20250203150418.7f244827@kernel.org> (raw)
In-Reply-To: <BL0PR11MB2913B949D05B9BB73108A5FFE7F52@BL0PR11MB2913.namprd11.prod.outlook.com>
On Mon, 3 Feb 2025 14:58:12 +0000 Woojung.Huh@microchip.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
next prev parent reply other threads:[~2025-02-03 23:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 16:14 KSZ9477 HSR Offloading Frieder Schrempf
2025-01-28 17:51 ` Andrew Lunn
2025-01-29 7:24 ` Frieder Schrempf
2025-01-29 8:03 ` Frieder Schrempf
2025-01-29 11:17 ` Lukasz Majewski
2025-01-29 11:35 ` Frieder Schrempf
2025-01-29 13:26 ` Andrew Lunn
2025-01-29 13:58 ` Lukasz Majewski
2025-01-29 17:07 ` Frieder Schrempf
2025-01-29 18:57 ` Woojung.Huh
2025-01-30 8:43 ` Frieder Schrempf
2025-01-30 14:17 ` Woojung.Huh
2025-02-03 9:31 ` Lukasz Majewski
2025-02-03 14:43 ` Woojung.Huh
2025-02-03 14:47 ` Frieder Schrempf
2025-02-03 14:58 ` Woojung.Huh
2025-02-03 23:04 ` Jakub Kicinski [this message]
2025-02-04 14:55 ` Woojung.Huh
2025-08-13 13:43 ` Frieder Schrempf
2025-08-13 13:54 ` Łukasz Majewski
2025-08-13 15:42 ` Frieder Schrempf
2025-08-14 22:55 ` Andrew Lunn
2025-01-29 22:52 ` Lukasz Majewski
2025-01-30 10:19 ` Frieder Schrempf
2025-01-30 10:36 ` Frieder Schrempf
2025-01-30 13:39 ` Andrew Lunn
2025-01-29 13:14 ` Andrew Lunn
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=20250203150418.7f244827@kernel.org \
--to=kuba@kernel.org \
--cc=Tristram.Ha@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=frieder.schrempf@kontron.de \
--cc=lukma@denx.de \
--cc=netdev@vger.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.