From: Jakub Kicinski <kuba@kernel.org>
To: Suman Ghosh <sumang@marvell.com>
Cc: "pabeni@redhat.com" <pabeni@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [EXT] Re: [PATCH V3] octeontx2-pf: Add support for adaptive interrupt coalescing
Date: Tue, 10 May 2022 13:03:14 -0700 [thread overview]
Message-ID: <20220510130314.15a5e4fa@kernel.org> (raw)
In-Reply-To: <SJ0PR18MB5216F9A48501F795382D41BDDBC99@SJ0PR18MB5216.namprd18.prod.outlook.com>
On Tue, 10 May 2022 04:18:39 +0000 Suman Ghosh wrote:
> Hi Jakub,
>
> Yes, this is tested code.
Alright, rebase, retest, repost then please.
As I said the current version does not apply:
$ git checkout net-next/master
HEAD is now at ecd17a87eb78 x25: remove redundant pointer dev
$ git pw series apply 638987
Applying: octeontx2-pf: Add support for adaptive interrupt coalescing
error: sha1 information is lacking or useless (drivers/net/ethernet/marvell/octeontx2/Kconfig).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 octeontx2-pf: Add support for adaptive interrupt coalescing
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
prev parent reply other threads:[~2022-05-10 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 5:45 [PATCH V3] octeontx2-pf: Add support for adaptive interrupt coalescing Suman Ghosh
2022-05-10 0:41 ` Jakub Kicinski
2022-05-10 0:42 ` Jakub Kicinski
2022-05-10 4:18 ` [EXT] " Suman Ghosh
2022-05-10 20:03 ` 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=20220510130314.15a5e4fa@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgoutham@marvell.com \
--cc=sumang@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 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.