Open Source Telephony
 help / color / mirror / Atom feed
From: Mario Tokarz <mario@tokarz.eu>
To: ofono@ofono.org
Subject: Re: [RFC 3/3] dun_dt: Add baseline for dun_dt plug-in.
Date: Sun, 10 Jul 2011 23:07:23 +0200	[thread overview]
Message-ID: <20110710210723.GA3206@mario-laptop> (raw)
In-Reply-To: <20110707165932.GA16322@joana>

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

Hi Gustavo,

On Thu, Jul 07, 2011 at 01:59:32PM -0300 , Gustavo Padovan wrote:
> Hi Mario,
> 
> * Mario Tokarz <mario@tokarz.eu> [2011-07-07 10:45:23 +0200]:
> 
> > From: Mario Tokarz <mario.tokarz@bmw-carit.de>
> > --- /dev/null
> > +++ b/plugins/dun_dt.c
> > @@ -0,0 +1,337 @@
> > +/*
> > + *
> > + *  oFono - Open Source Telephony
> > + *
> > + *  Copyright (C) 2008-2010  Intel Corporation. All rights reserved.
> > + *  Copyright (C) 2010  ProFUSION embedded systems
> 
> So this is mine as in the original code I wrote. Not from ProFUSION.
> It was part of a Google Summer of Code project.
> 
> 	Copyright (C) 2010 Gustavo Padovan <gustavo@padovan.org>
> 

Ah, ok - sorry for that. I based it on plugins/hfp_hc.c, so maybe the
Copyright Notice would need update on that file as well?

> > +
> > +	strcpy(alias_buf, "DUN ");
> > +	strcat(alias_buf, alias);
> 
> Do you really need tell the user this is a DUN modem? It doesn't care.
> 

Hm, ok. I'll look into that again then. I will be back with an
update. 

Thanks for taking the time to look over that.
Mario

      reply	other threads:[~2011-07-10 21:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07  8:45 [RFC 0/3] Adding DUN support Mario Tokarz
2011-07-07  8:45 ` [RFC 1/3] dunmodem: Add baseline for DUN modem driver Mario Tokarz
2011-07-07  8:16   ` Denis Kenzior
2011-07-07  8:45 ` [RFC 2/3] bluetooth: Add UUID for DUN Mario Tokarz
2011-07-07  8:00   ` Denis Kenzior
2011-07-07  8:45 ` [RFC 3/3] dun_dt: Add baseline for dun_dt plug-in Mario Tokarz
2011-07-07 16:59   ` Gustavo Padovan
2011-07-10 21:07     ` Mario Tokarz [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=20110710210723.GA3206@mario-laptop \
    --to=mario@tokarz.eu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox