Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Stefan Schmidt <stefan@osg.samsung.com>
Cc: linux-wpan@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [RFC bluetooth-next] atusb: add support for at86rf230
Date: Wed, 27 May 2015 13:46:38 +0200	[thread overview]
Message-ID: <20150527114635.GD712@omega> (raw)
In-Reply-To: <5565838F.60107@osg.samsung.com>

Hi Stefan,

On Wed, May 27, 2015 at 10:42:55AM +0200, Stefan Schmidt wrote:
> Hello.
> 
> On 24/05/15 14:43, Alexander Aring wrote:
> >This patch adds support for the at86rf230 version check which is used
> >by the rzusb stick.
> >
> >Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> >Cc: Stefan Schmidt <stefan@osg.samsung.com>
> >---
> >  drivers/net/ieee802154/atusb.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/drivers/net/ieee802154/atusb.c b/drivers/net/ieee802154/atusb.c
> >index 1e18774..5b6bb9a 100644
> >--- a/drivers/net/ieee802154/atusb.c
> >+++ b/drivers/net/ieee802154/atusb.c
> >@@ -515,7 +515,7 @@ static int atusb_get_and_show_chip(struct atusb *atusb)
> >  			man_id_1, man_id_0);
> >  		goto fail;
> >  	}
> >-	if (part_num != 3) {
> >+	if (part_num != 3 && part_num != 2) {
> >  		dev_err(&usb_dev->dev,
> >  			"unexpected transceiver, part 0x%02x version 0x%02x\n",
> >  			part_num, version_num);
> 
> Reviewed-by: Stefan Schmidt <stefan@osg.samsung.com>
> 

is this patch okay, even when it's the same product id? Possible
"stronger" test would be to check if atusb then part_num != 3, if rzusb
then != 2. Or can we add support for this later?

- Alex

  reply	other threads:[~2015-05-27 11:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24 12:43 [RFC bluetooth-next] atusb: add support for at86rf230 Alexander Aring
2015-05-27  6:54 ` Alexander Aring
2015-05-27  8:47   ` Stefan Schmidt
2015-05-27  8:42 ` Stefan Schmidt
2015-05-27 11:46   ` Alexander Aring [this message]
2015-05-27 11:49     ` 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:
  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=20150527114635.GD712@omega \
    --to=alex.aring@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-wpan@vger.kernel.org \
    --cc=stefan@osg.samsung.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