Linux-WPAN Archive on
 help / color / Atom feed
From: Stefan Schmidt <>
Subject: pull-request: ieee802154 for net 2019-04-25
Date: Thu, 25 Apr 2019 18:03:11 +0200
Message-ID: <> (raw)

Hello Dave.

An update from ieee802154 for your *net* tree.

Another fix from Kangjie Lu to ensure better checking regmap updates in the
mcr20a driver. Nothing else I have pending for the final release.

If there are any problems let me know.


During the preparation of this pull request a workflow question on my side came
up and wonder if you (or some subsystem maintainer sending you pull requests)
does have a comment on this. The ieee802154 subsystem has a low activity in the
number of patches coming through it. I still wanted to pull from your net tree
regularly to test if changes have implications to it. During this pulls I often
end up with merge of the remote tracking branch. Which in the end could mean
that I would have something like 3-4 merge commits in my tree with only one
actual patch I want to send over to you. Feels and looks kind of silly to be

How do other handle this? Just merge once every rc? Merge just before sending a
pull request? Never merge, wait for Dave to pull and merge and do a pull of his
tree directly afterwards?

Stefan Schmidt

The following changes since commit 1c5c12ee308aacf635c8819cd4baa3bd58f8a8b7:

  net/ncsi: handle overflow when incrementing mac address (2019-04-23 21:15:15 -0700)

are available in the Git repository at:

  git:// ieee802154-for-davem-2019-04-25

for you to fetch changes up to 22e8860cf8f777fbf6a83f2fb7127f682a8e9de4:

  net: ieee802154: fix missing checks for regmap_update_bits (2019-04-24 20:15:15 +0200)

Kangjie Lu (1):
      net: ieee802154: fix missing checks for regmap_update_bits

 drivers/net/ieee802154/mcr20a.c | 6 ++++++
 1 file changed, 6 insertions(+)

             reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 16:03 Stefan Schmidt [this message]
2019-04-29 22:21 ` David Miller
2019-04-30 10:24   ` Stefan Schmidt

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-WPAN Archive on

Archives are clonable:
	git clone --mirror linux-wpan/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-wpan linux-wpan/ \
	public-inbox-index linux-wpan

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone