From: David Miller <davem@davemloft.net>
To: stilwellt@openlabs.co
Cc: linux-zigbee-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ieee802154: at86rf230: add support for rf233 chip
Date: Wed, 12 Mar 2014 00:06:04 -0400 (EDT) [thread overview]
Message-ID: <20140312.000604.2215858990248416668.davem@davemloft.net> (raw)
In-Reply-To: <1394497765-5288-1-git-send-email-stilwellt@openlabs.co>
From: Thomas Stilwell <stilwellt@openlabs.co>
Date: Mon, 10 Mar 2014 19:29:25 -0500
> The rf233 and rf231 are sufficiently similar that we can treat
> rf233 like rf231.
>
> rf233 is missing some features that rf231 has, but we don't currently
> make use of them so there's nothing to handle differently yet.
>
> Should we add support in the future for rf231 *_NOCLK or SLEEP states,
> or PAD_IO drive strength, exceptions will need to be made for rf233.
>
> Signed-off-by: Thomas Stilwell <stilwellt@openlabs.co>
Applied, thank you.
prev parent reply other threads:[~2014-03-12 4:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 0:29 [PATCH net-next] ieee802154: at86rf230: add support for rf233 chip Thomas Stilwell
2014-03-12 4:06 ` David Miller [this message]
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=20140312.000604.2215858990248416668.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=stilwellt@openlabs.co \
/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).