All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeed@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Leon Romanovsky <leonro@nvidia.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [pull-request] mlx5-next branch 2021-12-15
Date: Wed, 15 Dec 2021 16:55:33 -0800	[thread overview]
Message-ID: <e54c8c88254d7768ba7a7dfbdfc798ce90bf17ab.camel@kernel.org> (raw)
In-Reply-To: <20211215154403.40563759@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Wed, 2021-12-15 at 15:44 -0800, Jakub Kicinski wrote:
> On Wed, 15 Dec 2021 15:35:09 -0800 Saeed Mahameed wrote:
> > On Wed, 2021-12-15 at 14:58 -0800, Jakub Kicinski wrote:
> > > On Wed, 15 Dec 2021 22:14:11 +0000 Saeed Mahameed wrote:  
> > > > already posted before :
> > > > [1] https://lore.kernel.org/netdev/20211201193621.9129-1-
> > > > saeed@kernel.org/
> > > > [2] https://lore.kernel.org/lkml/20211208141722.13646-1-
> > > > shayd@nvidia.com/ 
> > > 
> > > Post them as a reply to the pull request like you usually do,
> > > please.  
> > 
> > They were already posted, and reviewed, and all maintainers were
> > CC'ed,
> > including you, why do you want me to spam the mailing list over and
> > over again with the same patches ?
> 
> You reposting measly 5 patches is hardly spamming. I have scripts
> which

That's not the point, sometimes it is less or much more than 5.
For mlx5-next (Shared branch between RDMA and netdev), I would like to
submit standard clean PRs like all other maintainers.

> check if the contents of the PR match the posting, which obviously
> can't follow random links from the email.
> 

The script is great to validate pseudo-PRs (netdev only) where we post
patches for the first time in the PR.

but this is different, this is a true clean PR where all patches
already posted and reviewed. the tree is already written genuinely in
ink!

> > This is not how genuine pull requests are supposed to work.
> 
> I'm not comfortable with blindly pulling patches from vendor trees.

Good to know and very disappointing, is there anything i could do to
make you better trust my mlx5-next PRs ? other than RE-posting ?

Again I don't see any point of RE-posting the patches together with a
clean PR, redundant and unnecessary and against all standards, it just
cancels the whole process and duplicates my work, and will confuse
other maintainers who might have already pulled part or all of the
patches in the branch.




  reply	other threads:[~2021-12-16  0:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 18:49 [pull-request] mlx5-next branch 2021-12-15 Saeed Mahameed
2021-12-15 19:23 ` Jakub Kicinski
2021-12-15 22:14   ` Saeed Mahameed
2021-12-15 22:58     ` Jakub Kicinski
2021-12-15 23:35       ` Saeed Mahameed
2021-12-15 23:44         ` Jakub Kicinski
2021-12-16  0:55           ` Saeed Mahameed [this message]
2021-12-15 22:41   ` Saeed Mahameed

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=e54c8c88254d7768ba7a7dfbdfc798ce90bf17ab.camel@kernel.org \
    --to=saeed@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jgg@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.