From: Andrea Claudi <aclaudi@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Leon Romanovsky <leon@kernel.org>,
Jiri Pirko <jiri@resnulli.us>, Jon Maloy <jmaloy@redhat.com>,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH iproute2 2/2] treewide: fix typos in various comments
Date: Fri, 12 Jan 2024 12:23:37 +0100 [thread overview]
Message-ID: <ZaEhOak-a16AWxnd@renaissance-vector> (raw)
In-Reply-To: <20240111114035.4dc407dd@hermes.local>
On Thu, Jan 11, 2024 at 11:40:35AM -0800, Stephen Hemminger wrote:
> On Tue, 9 Jan 2024 17:32:35 +0100
> Andrea Claudi <aclaudi@redhat.com> wrote:
>
> > diff --git a/include/libiptc/libiptc.h b/include/libiptc/libiptc.h
> > index 1bfe4e18..89dce2f9 100644
> > --- a/include/libiptc/libiptc.h
> > +++ b/include/libiptc/libiptc.h
> > @@ -80,7 +80,7 @@ int iptc_append_entry(const xt_chainlabel chain,
> > const struct ipt_entry *e,
> > struct xtc_handle *handle);
> >
> > -/* Check whether a mathching rule exists */
> > +/* Check whether a matching rule exists */
> > int iptc_check_entry(const xt_chainlabel chain,
> > const struct ipt_entry *origfw,
> > unsigned char *matchmask,
>
> This is no longer in current code tree.
> Please rebase and resubmit
Woops, sorry. Will do.
prev parent reply other threads:[~2024-01-12 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 16:32 [PATCH iproute2 0/2] Fix some more typos in docs and comments Andrea Claudi
2024-01-09 16:32 ` [PATCH iproute2 1/2] docs, man: fix some typos Andrea Claudi
2024-01-10 10:35 ` Petr Machata
2024-01-11 17:21 ` Stephen Hemminger
2024-01-11 19:39 ` Stephen Hemminger
2024-01-09 16:32 ` [PATCH iproute2 2/2] treewide: fix typos in various comments Andrea Claudi
2024-01-10 10:54 ` Petr Machata
2024-01-11 19:40 ` Stephen Hemminger
2024-01-12 11:23 ` Andrea Claudi [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=ZaEhOak-a16AWxnd@renaissance-vector \
--to=aclaudi@redhat.com \
--cc=dsahern@gmail.com \
--cc=jiri@resnulli.us \
--cc=jmaloy@redhat.com \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 NNTP newsgroup(s).