From: Jason Gunthorpe <jgg@nvidia.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Cindy Lu <lulu@redhat.com>,
jasowang@redhat.com, yi.l.liu@intel.com,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [RFC v1 0/8] vhost-vdpa: add support for iommufd
Date: Fri, 10 Nov 2023 10:00:08 -0400 [thread overview]
Message-ID: <20231110140008.GM4488@nvidia.com> (raw)
In-Reply-To: <20231109183407-mutt-send-email-mst@kernel.org>
On Thu, Nov 09, 2023 at 06:48:46PM -0500, Michael S. Tsirkin wrote:
> On Tue, Nov 07, 2023 at 11:52:17AM -0400, Jason Gunthorpe wrote:
> > On Tue, Nov 07, 2023 at 09:30:21AM -0500, Michael S. Tsirkin wrote:
> > > On Tue, Nov 07, 2023 at 10:12:37AM -0400, Jason Gunthorpe wrote:
> > > > Big company's should take the responsibility to train and provide
> > > > skill development for their own staff.
> > >
> > > That would result in a beautiful cathedral of a patch. I know this is
> > > how some companies work. We are doing more of a bazaar thing here,
> > > though. In a bunch of subsystems it seems that you don't get the
> > > necessary skills until you have been publically shouted at by
> > > maintainers - better to start early ;). Not a nice environment for
> > > novices, for sure.
> >
> > In my view the "shouting from maintainers" is harmful to the people
> > buidling skills and it is an unkind thing to dump employees into that
> > kind of situation.
> >
> > They should have help to establish the basic level of competence where
> > they may do the wrong thing, but all the process and presentation of
> > the wrong thing is top notch. You get a much better reception.
>
> What - like e.g. mechanically fixing checkpatch warnings without
> understanding?
No, not at all. I mean actually going through and explaining what the
idea is to another person and ensuing that the commit messages convey
that idea, that the patches reflect the idea, that everything is
convayed, and it isn't obviously internally illogical.
Like, why did this series have a giant block of #ifdef 0'd code with
no explanation at all? That isn't checkpatch nitpicks, that is not
meeting the minimum standard to convey an idea in an RFC.
Jason
next prev parent reply other threads:[~2023-11-10 14:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231103171641.1703146-1-lulu@redhat.com>
2023-11-06 4:11 ` [RFC v1 0/8] vhost-vdpa: add support for iommufd Jason Wang
[not found] ` <20231103171641.1703146-8-lulu@redhat.com>
2023-11-06 7:25 ` [RFC v1 7/8] vp_vdpa::Add " Jason Wang
[not found] ` <20231103171641.1703146-9-lulu@redhat.com>
2023-11-06 7:26 ` [RFC v1 8/8] iommu: expose the function iommu_device_use_default_domain Jason Wang
[not found] ` <CACLfguUPZVY2HDBoir67u0CeR3A9wHjCGvuc3cGLe0L43f8jkg@mail.gmail.com>
2023-11-08 3:03 ` Jason Wang
2023-11-08 7:05 ` Cindy Lu
[not found] ` <20231103171641.1703146-4-lulu@redhat.com>
2023-11-06 7:27 ` [RFC v1 3/8] vhost: Add 3 new uapi to support iommufd Jason Wang
2023-11-06 7:30 ` Jason Wang
[not found] ` <CACLfguX9-wEQPUyZkJZoRMmgPDRFNyZCmt0nvHROhyP1yooiYA@mail.gmail.com>
2023-11-08 3:03 ` Jason Wang
2023-11-08 6:38 ` Cindy Lu
2023-11-08 7:09 ` Jason Wang
2023-11-10 2:31 ` Jason Wang
2023-11-10 6:49 ` Cindy Lu
2023-11-07 7:30 ` [RFC v1 0/8] vhost-vdpa: add support for iommufd Michael S. Tsirkin
[not found] ` <20231107124902.GJ4488@nvidia.com>
2023-11-07 13:28 ` Michael S. Tsirkin
[not found] ` <20231107141237.GO4488@nvidia.com>
2023-11-07 14:30 ` Michael S. Tsirkin
[not found] ` <20231107155217.GQ4488@nvidia.com>
2023-11-09 23:48 ` Michael S. Tsirkin
2023-11-10 14:00 ` Jason Gunthorpe [this message]
2023-11-07 14:55 ` Michael S. Tsirkin
[not found] ` <20231107154848.GP4488@nvidia.com>
2023-11-07 16:11 ` Michael S. Tsirkin
2023-11-07 13:23 ` Michael S. Tsirkin
2024-01-10 22:25 ` Michael S. Tsirkin
2024-01-11 9:02 ` Cindy Lu
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=20231110140008.GM4488@nvidia.com \
--to=jgg@nvidia.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=yi.l.liu@intel.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).