From: Jakub Kicinski <kuba@kernel.org>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: davem@davemloft.net, pabeni@redhat.com,
linux-wpan@vger.kernel.org, alex.aring@gmail.com,
miquel.raynal@bootlin.com, netdev@vger.kernel.org
Subject: Re: pull-request: ieee802154 for net 2024-09-01
Date: Tue, 3 Sep 2024 11:42:57 -0700 [thread overview]
Message-ID: <20240903114257.7b906da2@kernel.org> (raw)
In-Reply-To: <20240901184213.2303047-1-stefan@datenfreihafen.org>
On Sun, 1 Sep 2024 20:42:13 +0200 Stefan Schmidt wrote:
> Simon Horman catched two typos in our headers. No functional change.
Is it okay if we merge these into net-next ?
On one hand they are unlikely^w guaranteed not to introduce
regressions, but on the other such trivial spelling fixes are
not at all urgent.
next prev parent reply other threads:[~2024-09-03 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 18:42 pull-request: ieee802154 for net 2024-09-01 Stefan Schmidt
2024-09-03 18:42 ` Jakub Kicinski [this message]
2024-09-03 18:52 ` Stefan Schmidt
2024-09-03 19:00 ` Jakub Kicinski
2024-09-03 19:10 ` 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=20240903114257.7b906da2@kernel.org \
--to=kuba@kernel.org \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.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 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.