All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/4] radio settings: allow for more than one property
Date: Fri, 22 Oct 2010 09:55:46 -0500	[thread overview]
Message-ID: <4CC1A5F2.6000900@gmail.com> (raw)
In-Reply-To: <C358A26273CF2948B8BCDBA661A581782A7D0933E3@NOK-EUMSG-03.mgdnok.nokia.com>

[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]

Hi Mika,

On 10/22/2010 09:21 AM, Mika.Liljeberg(a)nokia.com wrote:
> Hi Denis,
> 
>>> Thanks. Still, I'd vote for a common checkpatch script in 
>> the oFono tree. ;)
>>>
>>
>> Are you volunteering to maintain such a beast and make sure 
>> it is up to
>> date with the kernel upstream version?
> 
> Only if I get to decide on the coding style. Otherwise, I'm proposing you guys should do it. Anyway, this is just a friendly suggestion in with the o sav e everyone's time.
> 

Nice try ;)

>> Yes, so let me give you a case where your approach breaks:
>>
>> Set the RAT property, then run two GetProperties at the same 
>> time.  You
>> end up querying FastDormancy twice.
> 
> No you won't, because the second GetProperties query will be terminated right off the bat with ofono busy error. Again, see here:
>

I really don't want to argue about this.

SetProperty("TechnologyPreference", ..)
-> Sets RADIO_SETTINGS_MODE_CACHED

GetProperties() -> queries Fast dormancy
GetProperties() -> queries Fast dormancy
->

+	} else if (rs->driver->query_fast_dormancy) {
+		rs->driver->query_fast_dormancy(rs,
+					fast_dormancy_query_callback, rs);
+		dbus_message_unref(reply);
+		return NULL;
+	}
+

You never set pending in the FastDormancy case.

> 
> Understandable. Makes it difficult to improve on design patterns that have already been replicated, though.
> 

Nobody is against improving things, but please try to do it in the
appropriate forum.  E.g. and RFC to the mailing list or an IRC discussion.

Regards,
-Denis

  reply	other threads:[~2010-10-22 14:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 13:37 [PATCH 0/4] Support for fast dormancy - take 2 Mika Liljeberg
2010-10-07 13:37 ` [PATCH 1/4] radio settings: allow for more than one property Mika Liljeberg
2010-10-20 22:57   ` Denis Kenzior
2010-10-21  8:55     ` Mika.Liljeberg
2010-10-21 14:03       ` Denis Kenzior
2010-10-22  7:08         ` Mika.Liljeberg
2010-10-22 13:49           ` Denis Kenzior
2010-10-22 14:21             ` Mika.Liljeberg
2010-10-22 14:55               ` Denis Kenzior [this message]
2010-10-25  6:59                 ` Mika.Liljeberg
2010-10-07 13:37 ` [PATCH 2/4] radio settings: add FastDormancy property Mika Liljeberg
2010-10-20 23:07   ` Denis Kenzior
2010-10-07 13:37 ` [PATCH 3/4] radio settings: document " Mika Liljeberg
2010-10-07 15:34   ` Marcel Holtmann
2010-10-08  6:56     ` Mika.Liljeberg
2010-10-08  8:55       ` Marcel Holtmann
2010-10-20 23:21   ` Denis Kenzior
2010-10-07 13:37 ` [PATCH 4/4] test: add scripts to enable and disable fast dormancy Mika Liljeberg
2010-10-20 23:09   ` Denis Kenzior
  -- strict thread matches above, loose matches on Subject: below --
2010-10-07 13:21 [PATCH 0/4] Support for fast formancy Mika Liljeberg
2010-10-07 13:21 ` [PATCH 1/4] radio settings: allow for more than one property Mika Liljeberg

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=4CC1A5F2.6000900@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.