netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: netdev@vger.kernel.org
Cc: Jay Vosburgh <j.vosburgh@gmail.com>,
	Veaceslav Falico <vfalico@gmail.com>,
	Andy Gospodarek <andy@greyhouse.net>,
	"David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Richard Cochran <richardcochran@gmail.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Hangbin Liu <liuhangbin@gmail.com>
Subject: [PATCH net-next 0/2] net: define new hwtstamp flag and return it to userspace
Date: Wed, 29 Dec 2021 16:09:36 +0800	[thread overview]
Message-ID: <20211229080938.231324-1-liuhangbin@gmail.com> (raw)

This patchset defined the new hwtstamp flag HWTSTAMP_FLAG_BONDED_PHC_INDEX
to make userspace program build pass with old kernel header by settting ifdef.

Let's also return the flag when do SIOC[G/S]HWTSTAMP to let userspace know
that it's necessary for a given netdev.

Hangbin Liu (2):
  net_tstamp: define new flag HWTSTAMP_FLAG_BONDED_PHC_INDEX
  Bonding: return HWTSTAMP_FLAG_BONDED_PHC_INDEX to notify user space

 drivers/net/bonding/bond_main.c | 42 ++++++++++++++++++++-------------
 include/uapi/linux/net_tstamp.h |  1 +
 2 files changed, 27 insertions(+), 16 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-12-29  8:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29  8:09 Hangbin Liu [this message]
2021-12-29  8:09 ` [PATCH net-next 1/2] net_tstamp: define new flag HWTSTAMP_FLAG_BONDED_PHC_INDEX Hangbin Liu
2021-12-29 14:23   ` Richard Cochran
2021-12-29  8:09 ` [PATCH net-next 2/2] Bonding: return HWTSTAMP_FLAG_BONDED_PHC_INDEX to notify user space Hangbin Liu
2021-12-29 14:23   ` Richard Cochran
2021-12-29 22:20 ` [PATCH net-next 0/2] net: define new hwtstamp flag and return it to userspace 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=20211229080938.231324-1-liuhangbin@gmail.com \
    --to=liuhangbin@gmail.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=j.vosburgh@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=vfalico@gmail.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 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).