All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tanner Love <tannerlove.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, Tanner Love <tannerlove@google.com>
Subject: [PATCH net-next 0/3] net: update netdev_rx_csum_fault() print dump only once
Date: Thu, 22 Apr 2021 15:47:35 -0400	[thread overview]
Message-ID: <20210422194738.2175542-1-tannerlove.kernel@gmail.com> (raw)

From: Tanner Love <tannerlove@google.com>

First two patches implement DO_ONCE_LITE for non-fast-path "do once"
functionality. Third patch uses the feature in netdev_rx_csum_fault to
print dump only once.

Tanner Love (3):
  once: implement DO_ONCE_LITE for non-fast-path "do once" functionality
  once: replace uses of __section(".data.once") with DO_ONCE_LITE(_IF)?
  net: update netdev_rx_csum_fault() print dump only once

 fs/xfs/xfs_message.h      | 13 +++----------
 include/asm-generic/bug.h | 37 +++++++------------------------------
 include/linux/once.h      | 16 ++++++++++++++++
 include/linux/printk.h    | 23 +++--------------------
 kernel/trace/trace.h      | 13 +++----------
 net/core/dev.c            | 10 +++++++---
 6 files changed, 39 insertions(+), 73 deletions(-)

-- 
2.31.1.498.g6c1eba8ee3d-goog


             reply	other threads:[~2021-04-22 19:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 19:47 Tanner Love [this message]
2021-04-22 19:47 ` [PATCH net-next 1/3] once: implement DO_ONCE_LITE for non-fast-path "do once" functionality Tanner Love
2021-04-22 19:47 ` [PATCH net-next 2/3] once: replace uses of __section(".data.once") with DO_ONCE_LITE(_IF)? Tanner Love
2021-04-22 21:23   ` kernel test robot
2021-04-22 21:23     ` kernel test robot
2021-04-22 22:28   ` kernel test robot
2021-04-22 22:28     ` kernel test robot
2021-04-22 22:28   ` kernel test robot
2021-04-22 22:28     ` kernel test robot
2021-04-22 19:47 ` [PATCH net-next 3/3] net: update netdev_rx_csum_fault() print dump only once Tanner Love
2021-04-23  0:42   ` Yunsheng Lin

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=20210422194738.2175542-1-tannerlove.kernel@gmail.com \
    --to=tannerlove.kernel@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=tannerlove@google.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.