linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Shradha Gupta <shradhagupta@linux.microsoft.com>
Cc: linux-hyperv@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, Nipun Gupta <nipun.gupta@amd.com>,
	Yury Norov <yury.norov@gmail.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	Jonathan Cameron <Jonathan.Cameron@huwei.com>,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	Kevin Tian <kevin.tian@intel.com>, Long Li <longli@microsoft.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Rob Herring <robh@kernel.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Krzysztof Wilczy???~Dski <kw@linux.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Dexuan Cui <decui@microsoft.com>, Wei Liu <wei.liu@kernel.org>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Konstantin Taranov <kotaranov@microsoft.com>,
	Simon Horman <horms@kernel.org>,
	Leon Romanovsky <leon@kernel.org>,
	Maxim Levitsky <mlevitsk@redhat.com>,
	Erni Sri Satya Vennela <ernis@linux.microsoft.com>,
	Peter Zijlstra <peterz@infradead.org>,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	Paul Rosswurm <paulros@microsoft.com>,
	Shradha Gupta <shradhagupta@microsoft.com>
Subject: Re: [PATCH v6 0/5] Allow dyn MSI-X vector allocation of MANA
Date: Mon, 16 Jun 2025 18:11:48 -0700	[thread overview]
Message-ID: <20250616181148.2aed5dfe@kernel.org> (raw)
In-Reply-To: <20250612061055.GA20126@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>

On Wed, 11 Jun 2025 23:10:55 -0700 Shradha Gupta wrote:
> On Wed, Jun 11, 2025 at 08:54:16AM -0700, Jakub Kicinski wrote:
> > On Wed, 11 Jun 2025 07:09:44 -0700 Shradha Gupta wrote:  
> > > Changes in v6
> > >  * rebased to linux-next's v6.16-rc1 as per Jakub's suggestion  
> > 
> > I meant a branch, basically apply the patches on the v6.16-rc1 tag
> > and push it out to GitHub, kernel.org or somewhere else public.
> > Then we can pull it in and maintain the stable commit IDs.
> > No need to repost the patches, FWIW, just share the branch here
> > once you pushed it out..  
> 
> Oh, understood. Thanks for the clarity. Here is a github repo branch
> with the changes on v6.16-rc1 tag
> https://github.com/shradhagupta6/linux/tree/shradha_v6.16-rc1

The tag was good, but when I pulled it my check scripts complained:

Commit a19036b86845 ("net: mana: Allocate MSI-X vectors dynamically")
	committer Signed-off-by missing
	author email:    shradhagupta@linux.microsoft.com
	committer email: shradhagupta@microsoft.com
	Signed-off-by: Shradha Gupta <shradhagupta@linux.microsoft.com>

etc. You seem to have committed the patches with a slightly different
email address. Not a huge deal but better to fix it if we can.

So please base the tag. The code can stay the same just adjust the
committer or author/signoff email addrs. We can use this as an
opportunity to add Bjorn's email.

No need to repost the code just ping here once you updated the tag.

  reply	other threads:[~2025-06-17  1:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 14:09 [PATCH v6 0/5] Allow dyn MSI-X vector allocation of MANA Shradha Gupta
2025-06-11 14:10 ` [PATCH v6 1/5] PCI/MSI: Export pci_msix_prepare_desc() for dynamic MSI-X allocations Shradha Gupta
2025-06-13 22:03   ` Bjorn Helgaas
2025-06-11 14:10 ` [PATCH v6 2/5] PCI: hv: Allow dynamic MSI-X vector allocation Shradha Gupta
2025-06-13 22:03   ` Bjorn Helgaas
2025-06-11 14:10 ` [PATCH v6 3/5] net: mana: explain irq_setup() algorithm Shradha Gupta
2025-06-11 14:10 ` [PATCH v6 4/5] net: mana: Allow irq_setup() to skip cpus for affinity Shradha Gupta
2025-06-11 14:11 ` [PATCH v6 5/5] net: mana: Allocate MSI-X vectors dynamically Shradha Gupta
2025-06-11 15:54 ` [PATCH v6 0/5] Allow dyn MSI-X vector allocation of MANA Jakub Kicinski
2025-06-12  6:10   ` Shradha Gupta
2025-06-17  1:11     ` Jakub Kicinski [this message]
2025-06-17 10:53       ` Shradha Gupta
2025-06-17 22:00 ` patchwork-bot+netdevbpf

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=20250616181148.2aed5dfe@kernel.org \
    --to=kuba@kernel.org \
    --cc=Jonathan.Cameron@huwei.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anna-maria@linutronix.de \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=decui@microsoft.com \
    --cc=edumazet@google.com \
    --cc=ernis@linux.microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=horms@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=kotaranov@microsoft.com \
    --cc=kw@linux.com \
    --cc=kys@microsoft.com \
    --cc=leon@kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=longli@microsoft.com \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mlevitsk@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nipun.gupta@amd.com \
    --cc=pabeni@redhat.com \
    --cc=paulros@microsoft.com \
    --cc=peterz@infradead.org \
    --cc=robh@kernel.org \
    --cc=shradhagupta@linux.microsoft.com \
    --cc=shradhagupta@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=wei.liu@kernel.org \
    --cc=yury.norov@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).