From: Nick Krause <xerofoify@gmail.com>
To: chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
Cc: linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: solos-pci.c: Fix me
Date: Mon, 21 Jul 2014 13:42:01 -0400 [thread overview]
Message-ID: <CAPDOMVh7cx57GtxHk-_tmorSWSj6xci-YkDrecdCLJfTANbHAQ@mail.gmail.com> (raw)
In-Reply-To: <20140721091445.1ee700bb@thirdoffive.cmf.nrl.navy.mil>
On Mon, Jul 21, 2014 at 9:14 AM, chas williams - CONTRACTOR
<chas@cmf.nrl.navy.mil> wrote:
> On Sun, 20 Jul 2014 00:59:42 -0400
> Nick Krause <xerofoify@gmail.com> wrote:
>
>> Hey Chas,
>> There seems to be a fix me in this file in the function, solos_bh.
>> Is the default statement correct and I remove the fix me or
>> does it need to be rewritten.
>> Cheers Nick
>>
>
> I am afraid that I don't know enough about the solos hardware to know
> if it needs to be rewritten. I gather the solos returns at least three
> kinds of packets, data, status and command. If you wish to eliminate
> the FIXME comment, you could just write:
>
> @@ -850,8 +850,7 @@ static void solos_bh(unsigned long card_arg)
> dev_kfree_skb_any(skb);
> break;
>
> - case PKT_COMMAND:
> - default: /* FIXME: Not really, surely? */
> + default: /* PKT_COMMAND */
> if (process_command(card, port, skb))
> break;power
> spin_lock(&card->cli_queue_lock);
>
> and be done with it since that will preserve existing behavior.
My only question then is this function causing bugs as is?
Cheers Nick
next prev parent reply other threads:[~2014-07-21 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 4:59 Nick Krause
2014-07-21 13:14 ` chas williams - CONTRACTOR
2014-07-21 17:42 ` Nick Krause [this message]
2014-07-21 18:18 ` chas williams - CONTRACTOR
2014-07-22 3:38 ` Nick Krause
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=CAPDOMVh7cx57GtxHk-_tmorSWSj6xci-YkDrecdCLJfTANbHAQ@mail.gmail.com \
--to=xerofoify@gmail.com \
--cc=chas@cmf.nrl.navy.mil \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®