linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <aspriel@gmail.com>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH py80211 0/4] py80211: add support for scheduled scan
Date: Sun, 21 Jun 2015 23:29:19 +0200	[thread overview]
Message-ID: <55872CAF.5080104@gmail.com> (raw)
In-Reply-To: <1434439990.3795.12.camel@coelho.fi>



On 16-06-15 09:33, Luca Coelho wrote:
> Hi Arend,
> 
> On Sat, 2015-06-13 at 08:26 +0200, Arend van Spriel wrote:
>> On 12-06-15 16:00, Luca Coelho wrote:
>>> Here's a small patchset that adds support for scheduled scans in
>>> py80211.
>>
>> Thanks! One general remark. It seems you are using soft-tabs where I
>> stick to true tabs. Python is pretty anal about that so better stick to
>> true tabs.
> 
> Uh, sorry about this.  I just used what emacs does by default in
> python-mode and didn't give this much thought.  I'll make sure my future
> patches conform to pythonist tab analities. :)

No problem. I am wondering if this is common to python projects.

>>> I'm not sure this is the right approach, I added separate classes for
>>> each command, so feel free to ask me to change it completely if you
>>> want and I may or may not do it. :P
>>
>> Me neither, but it may be a bit too classy ;-) So I would prefer to have
>> a scheduled scan class with start and stop operation.
> 
> Yeah, I thought so too... In any case, I saw that you applied the classy
> version.  Shall I rework this and send new patches or shall we leave it
> as it is?

I did not have too strong opinion about it to bounce it back at you.
Let's leave it for now.

Regards,
Arend

>> Good to see you are using '_' consistently for class private members and
>> functions. I need to clean it up in other files. I recently added Pyro
>> support allowing remote access to py80211 objects and it only exposes
>> public members and functions.
> 
> Yeah, I like the idea of being strict about private versus public
> visibility.
> 
> There was a small mistake in one of the changes you made.  I'm going to
> send a fix for it in a second.
> 
> Thanks for your help!
> 
> --
> Luca.
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in

      reply	other threads:[~2015-06-21 21:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 14:00 [PATCH py80211 0/4] py80211: add support for scheduled scan Luca Coelho
2015-06-12 14:00 ` [PATCH py80211 1/4] py80211: scan: spin base scan classes off scan_request Luca Coelho
2015-06-13 18:40   ` Arend van Spriel
2015-06-12 14:00 ` [PATCH py80211 2/4] py80211: scan: add sched_scan start class Luca Coelho
2015-06-13 18:44   ` Arend van Spriel
2015-06-12 14:00 ` [PATCH py80211 3/4] py80211: add sched_scan stop class Luca Coelho
2015-06-13 18:45   ` Arend van Spriel
2015-06-12 14:00 ` [PATCH py80211 4/4] py80211: scan: add matchsets support for scheduled scans Luca Coelho
2015-06-13 18:45   ` Arend van Spriel
2015-06-13  6:26 ` [PATCH py80211 0/4] py80211: add support for scheduled scan Arend van Spriel
2015-06-16  7:33   ` Luca Coelho
2015-06-21 21:29     ` Arend van Spriel [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=55872CAF.5080104@gmail.com \
    --to=aspriel@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luca@coelho.fi \
    /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).