From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: RE: [PATCH 2/6] stemodem: add default case
Date: Wed, 27 Oct 2010 11:12:08 +0200 [thread overview]
Message-ID: <1288170728.3613.32.camel@aeonflux> (raw)
In-Reply-To: <C358A26273CF2948B8BCDBA661A581782A7DBDFCDA@NOK-EUMSG-03.mgdnok.nokia.com>
[-- Attachment #1: Type: text/plain, Size: 4300 bytes --]
Hi Mika,
> > > That must be a new policy then, considering that stemodem
> > is the only one that failed compilation. Feel free to fix
> > this one. The first two patches in the set are unrelated to
> > fast dormancy anyway.
> >
> > that is the whole point here. You modified the enum and the
> > compilation
> > should fail unless you add a statement for that new item.
> >
> > Let me make this clear, I do want the compilation to fail here and the
> > STE driver is doing the right thing.
>
> I understand that. As I said, feel free to fix. Fast dormancy patches 3-6 should apply just fine without the first two courtesy patches.
I am waiting for Denis review since he was looking at them initially.
Once these are applied, we can take care of the fallout.
> > There might be other cases where this is not consistent. I
> > would prefer
> > if that never happens, but somethings things slip through even close
> > code review. If you know other cases, please let me know and
> > we fix them
> > as well here.
>
> All the other drivers implementing radio settings. Here's a couple of examples:
>
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 134) switch (mode) {
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 135) case OFONO_RADIO_ACCESS_MODE_ANY:
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 136) value = 1;
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 137) break;
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 138) case OFONO_RADIO_ACCESS_MODE_GSM:
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 139) value = 0;
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 140) break;
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 141) case OFONO_RADIO_ACCESS_MODE_UMTS:
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 142) value = 2;
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 143) break;
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 144) default:
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 145) CALLBACK_WITH_FAILURE(cb, data);
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 146) g_free(cbd);
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 147) return;
> ac63fd95 (Marcel Holtmann 2010-09-23 23:27:08 +0900 148) }
>
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 133) switch (mode) {
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 134) case OFONO_RADIO_ACCESS_MODE_ANY:
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 135) value = 5;
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 136) break;
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 137) case OFONO_RADIO_ACCESS_MODE_GSM:
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 138) value = 0;
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 139) break;
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 140) case OFONO_RADIO_ACCESS_MODE_UMTS:
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 141) value = 1;
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 142) break;
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 143) default:
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 144) CALLBACK_WITH_FAILURE(cb, data);
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 145) g_free(cbd);
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 146) return;
> 30b054d0 (Marcel Holtmann 2010-06-06 15:18:57 -0700 147) }
>
> Sorry, couldn't resist. ;-)
I have no problem with that being pointing out. I actually encourage
people pointing this out. This is clearly myself being stupid. And good
thing is that this is open source, so I fixed it.
With a code base of 100k lines of code and more, such things happen. And
even with Denis and myself cross-reviewing each other this will still
happen. Sometimes things just slip through the cracks. Part of
development life. So once noticed this will be dealt with.
Regards
Marcel
next prev parent reply other threads:[~2010-10-27 9:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 15:31 [PATCH 0/6] Fast dormancy support Mika Liljeberg
2010-10-26 15:31 ` [PATCH 1/6] radio settings: fix mode initializion Mika Liljeberg
2010-10-28 3:27 ` Denis Kenzior
2010-10-26 15:31 ` [PATCH 2/6] stemodem: add default case Mika Liljeberg
2010-10-26 15:35 ` Marcel Holtmann
2010-10-26 15:43 ` Mika.Liljeberg
2010-10-26 16:24 ` Marcel Holtmann
2010-10-27 7:06 ` Mika.Liljeberg
2010-10-27 9:12 ` Marcel Holtmann [this message]
2010-10-26 15:31 ` [PATCH 3/6] radio settings: add FastDormancy property Mika Liljeberg
2010-10-28 3:27 ` Denis Kenzior
2010-10-28 13:32 ` Mika.Liljeberg
2010-10-28 15:19 ` Denis Kenzior
2010-10-29 8:52 ` Mika.Liljeberg
2010-10-29 14:34 ` Denis Kenzior
2010-11-01 9:18 ` Mika.Liljeberg
2010-10-26 15:31 ` [PATCH 4/6] test: add script to control fast dormancy Mika Liljeberg
2010-10-28 3:27 ` Denis Kenzior
2010-10-26 15:31 ` [PATCH 5/6] isimodem: add support for FastDormancy property Mika Liljeberg
2010-10-28 3:28 ` Denis Kenzior
2010-10-26 15:31 ` [PATCH 6/6] TODO: mark fast dormancy as done Mika Liljeberg
2010-10-28 3:28 ` Denis Kenzior
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=1288170728.3613.32.camel@aeonflux \
--to=marcel@holtmann.org \
--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.