From: Jakub Kicinski <kuba@kernel.org>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, rdunlap@infradead.org,
laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH net v3] docs: netdev: document patchwork patch states
Date: Fri, 1 Sep 2023 07:22:47 -0700 [thread overview]
Message-ID: <20230901072247.20f84171@kernel.org> (raw)
In-Reply-To: <ZPGjdQOfM2POGoEW@hog>
On Fri, 1 Sep 2023 10:40:21 +0200 Sabrina Dubroca wrote:
> > v3:
> > - clarify that patches once set to Awaiting Upstream will stay there
>
> mhmm, the patch looks identical to v2. Did you post the wrong version?
oops, forgot to commit, thanks for catching!
prev parent reply other threads:[~2023-09-01 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 1:41 [PATCH net v3] docs: netdev: document patchwork patch states Jakub Kicinski
2023-09-01 8:40 ` Sabrina Dubroca
2023-09-01 14:22 ` 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=20230901072247.20f84171@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=sd@queasysnail.net \
--cc=workflows@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).