public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
	Luis Rodriguez <Luis.Rodriguez@atheros.com>,
	Julia Lawall <julia@diku.dk>, "gregkh@suse.de" <gregkh@suse.de>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH 5/5] staging/otus: Move a dereference below a NULL test
Date: Mon, 13 Jul 2009 10:00:38 -0700	[thread overview]
Message-ID: <20090713170038.GA12919@mosca> (raw)
In-Reply-To: <4A5872FD.8040500@gmail.com>

On Sat, Jul 11, 2009 at 04:09:49AM -0700, Jiri Slaby wrote:
> On 07/11/2009 12:32 PM, Jaswinder Singh Rajput wrote:
> > And more funny thing is that all functions are global in this file.
> >
> > Greg, can you please check the scope of these function, why all are
> > global.
> 
> Why don't you do that? I think patches are welcome :).

I will note Otus has a replacement ar9170 driver already upstream,
as soon as it gets aggregation support otus will be dropped. Better
focus on ar9170 instead if you are looking to spend some cycles on
driver help.

  Luis

  reply	other threads:[~2009-07-13 17:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11  7:51 [PATCH 5/5] staging/otus: Move a dereference below a NULL test Julia Lawall
2009-07-11  8:17 ` Jiri Slaby
2009-07-11  8:31   ` Julia Lawall
2009-07-11 10:17   ` Jaswinder Singh Rajput
2009-07-11 10:32     ` Jaswinder Singh Rajput
2009-07-11 11:09       ` Jiri Slaby
2009-07-13 17:00         ` Luis R. Rodriguez [this message]
2009-07-11 11:06     ` Jiri Slaby
2009-07-11 11:32       ` Julia Lawall
2009-07-11 11:58         ` Julia Lawall
2009-07-11 17:03   ` Greg KH
2009-07-11 18:28     ` Julia Lawall

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=20090713170038.GA12919@mosca \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@atheros.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=jaswinder@kernel.org \
    --cc=jirislaby@gmail.com \
    --cc=julia@diku.dk \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@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