netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: Geetha sowjanya <gakula@marvell.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <sgoutham@marvell.com>,
	<davem@davemloft.net>, <sbhatta@marvell.com>,
	<hkelam@marvell.com>, <jerinj@marvell.com>,
	<lcherian@marvell.com>
Subject: Re: [net-next v3 00/14] Add Marvell CN10K support
Date: Thu, 4 Feb 2021 12:27:29 -0800	[thread overview]
Message-ID: <20210204122729.5b1b592a@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20210204120454.000054d6@intel.com>

On Thu, 4 Feb 2021 12:04:54 -0800 Jesse Brandeburg wrote:
> Geetha sowjanya wrote:
> 
> > v2-v3
> > Reposting as a single thread.  
> 
> FYI, it didn't work, suggest you try adding the git-send-email option
> (via git-config)
> 
> sendemail.thread=true
> sendemail.chainreplyto=false
> 
> And you can test locally by using first using git send-email to export
> to mbox and checking for References and In-Reply-to headers. Then
> sending for real.

And looks like there are build issues so you'll get a chance to try
again :/

Please make sure you don't add any new warnings to the build, with W=1
C=1 flags. Each patch must build cleanly.

Shooting from the hip something along the lines of:

 make allmodconfig
 current=$(make W=1 C=1 | wc -l)

 git rebase --exec '[ $current -eq $(make W=1 C=1 | wc -l) ]'

Please do not repost until the tree can build cleanly at every commit
of the series.

      reply	other threads:[~2021-02-04 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 11:24 [net-next v3 00/14] Add Marvell CN10K support Geetha sowjanya
2021-02-04 20:04 ` Jesse Brandeburg
2021-02-04 20:27   ` Jakub Kicinski [this message]

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=20210204122729.5b1b592a@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=lcherian@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.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).