netdev - Re: [PATCH v17 1/1] mctp pcc: Implement MCTP over PCC Transport

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: <Z7dwFKs-ysnJ2Rs4@LQ3V64L9R2>
Date: Thu, 20 Feb 2025 13:10:28 -0500
From: Joe Damato <jdamato@...tly.com>
To: Adam Young <admiyo@...eremail.onmicrosoft.com>
Cc: Jeremy Kerr <jk@...econstruct.com.au>, admiyo@...amperecomputing.com,
	Matt Johnston <matt@...econstruct.com.au>,
	Andrew Lunn <andrew+netdev@...n.ch>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	Sudeep Holla <sudeep.holla@....com>,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	Huisong Li <lihuisong@...wei.com>
Subject: Re: [PATCH v17 1/1] mctp pcc: Implement MCTP over PCC Transport

On Thu, Feb 20, 2025 at 12:31:21PM -0500, Adam Young wrote:
> On 2/6/25 19:30, Jeremy Kerr wrote:
> 
> > Hi Adam,
> > 
> > > Is that your only concern with this patch?
> > Yes, hence the ack. If there are other changes that you end up doing in
> > response to other reviews, then please address the spacing thing too,
> > but that certainly doesn't warrant a new revision on its own.
> > 
> > > What else would need to happen in order for this to get ACKed at this
> > > point?
> > It already has an ack from me.
> > 
> > As for actual merging: If the netdev maintainers have further reviews,
> > please address those. If not, I assume they would merge in this window.
> 
> Should I resubmit this patch with a title that includes net-next in order
> for it to be picked up?  I can see that there is stuff being pulled in and
> net-next for 6.14 is at RC2.

I am not a maintainer and I don't speak for them, but I've been
following this submission so my guess would be:
  - Fix the spacing issue Jeremy pointed out
  - Include Jeremy's ack in the updated patch
  - Submit a v18 with net-next in the subject line, an indicate in
    the cover letter the two changes you've made (spacing issue and
    adding Jeremy's ack).