From: Joe Perches <joe@perches.com>
To: netdev@vger.kernel.org
Cc: Tom Rix <trix@redhat.com>,
Michael Chan <michael.chan@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Jiri Pirko <jiri@nvidia.com>, Ido Schimmel <idosch@nvidia.com>,
Ariel Elior <aelior@marvell.com>,
GR-everest-linux-l2@marvell.com, linux-kernel@vger.kernel.org,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>
Subject: Re: [PATCH] ethernet: Remove invalid trailers after %pI4
Date: Sat, 26 Dec 2020 09:47:19 -0800 [thread overview]
Message-ID: <0d06aad61cdb5be1d9c8c17bcf938d726d028e3f.camel@perches.com> (raw)
In-Reply-To: <d1ea50ed47e2e9ca65a67ffc2ca0eee08e662132.camel@perches.com>
On Sat, 2020-12-26 at 09:10 -0800, Joe Perches wrote:
> Alphanumeric characters after vsprintf pointer extension %pI4 are
> not valid and are not emitted.
>
> Remove the invalid characters from the %pI4 uses.
self-nak. I believe I misunderstood the format specifier.
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] ethernet: Remove invalid trailers after %pI4
Date: Sat, 26 Dec 2020 09:47:19 -0800 [thread overview]
Message-ID: <0d06aad61cdb5be1d9c8c17bcf938d726d028e3f.camel@perches.com> (raw)
In-Reply-To: <d1ea50ed47e2e9ca65a67ffc2ca0eee08e662132.camel@perches.com>
On Sat, 2020-12-26 at 09:10 -0800, Joe Perches wrote:
> Alphanumeric characters after vsprintf pointer extension %pI4 are
> not valid and are not emitted.
>
> Remove the invalid characters from the %pI4 uses.
self-nak. I believe I misunderstood the format specifier.
next prev parent reply other threads:[~2020-12-26 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 17:10 [PATCH] ethernet: Remove invalid trailers after %pI4 Joe Perches
2020-12-26 17:10 ` [Intel-wired-lan] " Joe Perches
2020-12-26 17:47 ` Joe Perches [this message]
2020-12-26 17:47 ` Joe Perches
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=0d06aad61cdb5be1d9c8c17bcf938d726d028e3f.camel@perches.com \
--to=joe@perches.com \
--cc=GR-everest-linux-l2@marvell.com \
--cc=aelior@marvell.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=trix@redhat.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.