From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 09DFA23FC54; Thu, 19 Jun 2025 14:55:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750344946; cv=none; b=ARuRlXh/e6CYZQhnupED6O/a6IObEHl7irP9Vs8VfNSvXIY4vruS+QZNtzWNMVBpxqrIV1EsUiCjd5Ce2pP+d1XzanWLaU0R7f0uVatxQd4o692KFNxVJXEAQ9yUitz/aCCFqyNbvxHkhYq0AJVkLgaqb2q/3qlVq3frkrt1ifM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750344946; c=relaxed/simple; bh=ZCXeVi5NAoQxiaYJvq5NPU85M46dLEnN6Ij6bmOHHO4=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=c2PR0ffeVbCP4coHtthClAIXZEdISuInyEE42X45lkicOUSnjuUlL7fhJnigxVTZ56XATBSE7m3m2o6jrJv4u50+fxDCN81t+pU94HdmhGM3sMUdpDfWaJzGgJgUov3PlI2dEbV5o+C5WVgeMKCfr5vvC6KwoJqY4LAVWNU8O4Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=rjvvEUjH; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="rjvvEUjH" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D60FFC4CEF0; Thu, 19 Jun 2025 14:55:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1750344945; bh=ZCXeVi5NAoQxiaYJvq5NPU85M46dLEnN6Ij6bmOHHO4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=rjvvEUjHWVl9rLIeg1IMdGFdNd+KYoSmLb0gjCRNJ3ydRW7kRFoO2XHRm8gdsvF2p FyFEs0reGeXdXuBM3o7OFimmv1c+7160wM+pbi2P+acQTRKmu0LnnG0ZxpYJsCg/6v ucXphXMhCgF3keVLw+N/1FQ9th7RuhLHVxEnN4FlPQcX4+AwqHRSUYDbn5tVXTILWm lvinXcJOkEIT2e4f2AnZm9VV4HF4cGwOWwVDW1HTavUA6B6ClO6n0iZWJAVF6sOO3a ZvskE9It4FYPMmPy+tqleWNi7dTaim827SN3Ax7ifh44yBNtElE37NwTgwIjwPPZnd mLyhS9G6WBVMg== Date: Thu, 19 Jun 2025 07:55:43 -0700 From: Jakub Kicinski To: Mark Bloch Cc: "David S. Miller" , Paolo Abeni , Eric Dumazet , "Andrew Lunn" , Simon Horman , , , , , Leon Romanovsky , Jonathan Corbet , , , , Subject: Re: [PATCH net-next 0/5] net/mlx5e: Add support for PCIe congestion events Message-ID: <20250619075543.1d31f937@kernel.org> In-Reply-To: <20250619113721.60201-1-mbloch@nvidia.com> References: <20250619113721.60201-1-mbloch@nvidia.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 `_. 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