From: Alexander Aring <alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: alex.bluesman.smirnov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-zigbee-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [PATCH net-next v2 0/2] ieee802154: Kconfig fixes
Date: Tue, 4 Mar 2014 19:01:16 +0100 [thread overview]
Message-ID: <1393956078-6950-1-git-send-email-alex.aring@gmail.com> (raw)
Hi,
this patch series fix some issues with Kconfig in the ieee802154 subsystem.
changes since v2:
- Add commit summary in commit msg of patch 1/2.
- move one line whitespace fix of at86rf230 entry from patch 2/2 to 1/2.
Alexander Aring (2):
at86rf230: add help and 212 to Kconfig menu entry
ieee802154: fix whitespace issues in Kconfig
drivers/net/ieee802154/Kconfig | 34 ++++++++++++++++++++--------------
net/ieee802154/Kconfig | 2 +-
2 files changed, 21 insertions(+), 15 deletions(-)
--
1.9.0
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
next reply other threads:[~2014-03-04 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 18:01 Alexander Aring [this message]
[not found] ` <1393956078-6950-1-git-send-email-alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-04 18:01 ` [PATCH net-next v2 1/2] at86rf230: add help and 212 to Kconfig menu entry Alexander Aring
2014-03-04 18:01 ` [PATCH net-next v2 2/2] ieee802154: fix whitespace issues in Kconfig Alexander Aring
2014-03-05 1:13 ` [PATCH net-next v2 0/2] ieee802154: Kconfig fixes David Miller
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=1393956078-6950-1-git-send-email-alex.aring@gmail.com \
--to=alex.aring-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=alex.bluesman.smirnov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-zigbee-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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).