Re: [PATCH net-next 0/5] net/mlx5e: Add support for PCIe congestion events

[Jakub Kicinski]

On Thu, 19 Jun 2025 14:37:16 +0300 Mark Bloch wrote:
> PCIe congestion events are events generated by the firmware when the
> device side has sustained PCIe inbound or outbound traffic above
> certain thresholds. The high and low threshold are hysteresis thresholds
> to prevent flapping: once the high threshold has been reached, a low
> threshold event will be triggered only after the bandwidth usage went
> below the low threshold.

What are we supposed to do with a series half of which is tagged for
one tree and half for another? If you want for some of the patches to
go via the shared tree - you have to post them separately.
Ideally you'd post them to the list in a combined "pull request +
patches" format (see for example how Marc posts CAN patches, or Pablo
posts netfilter). Once we pull that you can sent the net-next stuff
separately as patches.

I feel like I just had the same exact conversation with Tariq recently.
Really not great when same process explainer has to be given to
multiple people from the same company :( I'd like to remind y'all that
reading the mailing list is not optional:

  Mailing list participation
  --------------------------
  
  Linux kernel uses mailing lists as the primary form of communication.
  Maintainers must be subscribed and follow the appropriate subsystem-wide
  mailing list. Either by subscribing to the whole list or using more
  modern, selective setup like
  `lei <https://people.kernel.org/monsieuricon/lore-lei-part-1-getting-started>`_.
  
See: https://www.kernel.org/doc/html/next/maintainer/feature-and-driver-maintainers.html#mailing-list-participation

Then again, I guess you're not a maintainer. There are 2 maintainers
for the driver listed and yet we get patches from a 3rd unlisted person.

SMH