From: Jakub Kicinski <kuba@kernel.org>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<idosch@idosch.org>, <brett.creeley@amd.com>,
<drivers@pensando.io>
Subject: Re: [PATCH v2 net-next 1/5] ionic: remove dead device fail path
Date: Thu, 13 Jul 2023 19:57:30 -0700 [thread overview]
Message-ID: <20230713195730.24afb3ee@kernel.org> (raw)
In-Reply-To: <20230713192936.45152-2-shannon.nelson@amd.com>
On Thu, 13 Jul 2023 12:29:32 -0700 Shannon Nelson wrote:
> Note: This patch is cherry-picked from commit 3a7af34fb6e
> because the following patchset is dependent on this
> change. This patch can be dropped from this series
> once net-next is updated
Doesn't work, I tested applying the series after merging the trees -
git am doesn't skip this cleanly so our scripts get confused and
end up making a real mess of the branches. Let's stick to the
documented process. You'll have to repost without this patch.
--
pw-bot: cr
next prev parent reply other threads:[~2023-07-14 2:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 19:29 [PATCH v2 net-next 0/5] ionic: add FLR support Shannon Nelson
2023-07-13 19:29 ` [PATCH v2 net-next 1/5] ionic: remove dead device fail path Shannon Nelson
2023-07-14 2:57 ` Jakub Kicinski [this message]
2023-07-14 4:38 ` Shannon Nelson
2023-07-13 19:29 ` [PATCH v2 net-next 2/5] ionic: extract common bits from ionic_remove Shannon Nelson
2023-07-13 19:29 ` [PATCH v2 net-next 3/5] ionic: extract common bits from ionic_probe Shannon Nelson
2023-07-13 19:29 ` [PATCH v2 net-next 4/5] ionic: pull out common bits from fw_up Shannon Nelson
2023-07-13 19:29 ` [PATCH v2 net-next 5/5] ionic: add FLR recovery support Shannon Nelson
2023-07-14 2:21 ` [PATCH v2 net-next 0/5] ionic: add FLR support patchwork-bot+netdevbpf
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=20230713195730.24afb3ee@kernel.org \
--to=kuba@kernel.org \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=idosch@idosch.org \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@amd.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.