virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-pci@vger.kernel.org, llvm@lists.linux.dev,
	virtualization@lists.linux-foundation.org, bhelgaas@google.com,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH 3/3 v6] virtio: vdpa: new SolidNET DPU driver.
Date: Tue, 20 Dec 2022 18:20:56 -0500	[thread overview]
Message-ID: <20221220182026-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <Y6IfwHicoMojJrIB@dev-arch.thelio-3990X>

On Tue, Dec 20, 2022 at 01:49:04PM -0700, Nathan Chancellor wrote:
> On Tue, Dec 20, 2022 at 06:46:20PM +0200, Alvaro Karsz wrote:
> > Hi Nathan,
> > 
> > > This does not appear to be a false positive but what was the intent
> > > here? Should the local name variables increase their length or should
> > > the buffer length be reduced?
> > 
> > You're right, the local name variables and snprintf argument don't match.
> > Thanks for noticing.
> > I think that we should increase the name variables  to be
> > SNET_NAME_SIZE bytes long.
> > 
> > How should I proceed from here?
> > Should I create a new version for this patch, or should I fix it in a
> > follow up patch?
> 
> That is up to Michael at the end of the day (each maintainer handles
> their tree differently) but I would recommend sending a follow up fix,
> as it is easy to fold it in if they want to rebase the tree for it or
> just take it as a fix.
> 
> Thanks for the quick triage and response!
> 
> Cheers,
> Nathan

on top is ok but post soon please as i need to send this to Linus.

-- 
MST

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  parent reply	other threads:[~2022-12-20 23:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19  8:35 [RESEND PATCH 0/3] virtio: vdpa: new SolidNET DPU driver Alvaro Karsz
2022-12-19  8:35 ` [RESEND PATCH 1/3] Add SolidRun vendor id Alvaro Karsz
2022-12-29 19:55   ` Bjorn Helgaas
2022-12-29 21:06     ` Alvaro Karsz
2022-12-29 21:29       ` Bjorn Helgaas
2022-12-29 22:27         ` Michael S. Tsirkin
2022-12-19  8:35 ` [RESEND PATCH 2/3] New PCI quirk for SolidRun SNET DPU Alvaro Karsz
2022-12-29 19:55   ` Bjorn Helgaas
2022-12-19  8:35 ` [PATCH 3/3 v6] virtio: vdpa: new SolidNET DPU driver Alvaro Karsz
2022-12-19 10:43   ` Michael S. Tsirkin
2022-12-19 10:44     ` Michael S. Tsirkin
2022-12-19 10:49   ` Michael S. Tsirkin
2022-12-19 10:55     ` Alvaro Karsz
2022-12-19 11:03       ` Michael S. Tsirkin
2022-12-19 11:32         ` Alvaro Karsz
2022-12-19 16:40           ` Michael S. Tsirkin
2022-12-20  6:50   ` Jason Wang
2022-12-20  7:25     ` Alvaro Karsz
2022-12-20  8:54       ` Jason Wang
     [not found]   ` <Y6HjpvDfIusAz2uS@dev-arch.thelio-3990X>
2022-12-20 16:46     ` Alvaro Karsz
2022-12-20 21:48       ` Arnd Bergmann
     [not found]       ` <Y6IfwHicoMojJrIB@dev-arch.thelio-3990X>
2022-12-20 23:20         ` Michael S. Tsirkin [this message]
2022-12-21  6:40       ` Michael S. Tsirkin
2022-12-21  7:05         ` Alvaro Karsz

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=20221220182026-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=jdelvare@suse.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=virtualization@lists.linux-foundation.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 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).