linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kvalo@adurom.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
	Greg Dietsche <gregory.dietsche@cuw.edu>,
	linux-wireless@vger.kernel.org
Subject: Re: pull request: iwlegacy 2011-11-16
Date: Thu, 17 Nov 2011 14:03:08 -0500	[thread overview]
Message-ID: <20111117190307.GE32622@tuxdriver.com> (raw)
In-Reply-To: <87y5vf8ak3.fsf@purkki.adurom.net>

On Thu, Nov 17, 2011 at 09:36:44AM +0200, Kalle Valo wrote:
> Hi Stanislaw,
> 
> Stanislaw Gruszka <sgruszka@redhat.com> writes:
> 
> > Please pull iwlegacy cleanup changes done by Greg and me, intended
> > for 3.3. These request include huge patches with file renaming and
> > automatic code processing done by sed and indent. Driver is still
> > quite messy and need more cleanup, but these massive changes bring
> > driver close to the state that we could name it maintainable.
> >
> > Hopefully with having clean, maintainable code I will be able to fix
> > some nasty not easy reproducible bugs, we still have in the iwlegacy
> > driver.
> 
> I haven't seen these patches on linux-wireless mailing list at all.
> Isn't it recommended that all wireless patches are sent to
> linux-wireless for public review?

Yes, it is.  Please make sure to send these patches to the list for
review by the group.

Thanks,

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2011-11-17 19:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 12:22 pull request: iwlegacy 2011-11-16 Stanislaw Gruszka
2011-11-17  7:36 ` Kalle Valo
2011-11-17 19:03   ` John W. Linville [this message]
2011-11-18  7:30     ` Stanislaw Gruszka
2011-11-21 15:32       ` Kalle Valo

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=20111117190307.GE32622@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=gregory.dietsche@cuw.edu \
    --cc=kvalo@adurom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.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;
as well as URLs for NNTP newsgroup(s).