Open Source Telephony
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [patch 1/6] Add PPP protocol support with HDLC framing
Date: Sat, 20 Mar 2010 16:33:32 +0100	[thread overview]
Message-ID: <1269099212.2700.179.camel@localhost.localdomain> (raw)
In-Reply-To: <20100319124607.6655ec44@kcaccard-MOBL3>

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

Hi Kristen,

> This patch implements the basic PPP protocol.  LCP, NCP etc. are handled in a
> different patch.
> 
> ---
>  Makefile.am      |    4 
>  gatchat/gatppp.c |  133 ++++++++++++++++
>  gatchat/gatppp.h |   59 +++++++
>  gatchat/ppp.c    |  455 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  gatchat/ppp.h    |  130 +++++++++++++++
>  5 files changed, 780 insertions(+), 1 deletion(-)

please keep the patches whitespace clean. Otherwise you will make it
really hard and complicated for everybody if we have to do whitespace
cleanup in between patches.

Applying: Add PPP protocol support with HDLC framing
/data/devel/ofono/.git/rebase-apply/patch:572: space before tab in indent.
        	if (status != G_IO_STATUS_NORMAL && status != G_IO_STATUS_AGAIN)
/data/devel/ofono/.git/rebase-apply/patch:573: space before tab in indent.
                	return FALSE;
fatal: 2 lines add whitespace errors.

Using an editor that visualizes whitespaces and tabs might help here.

And empty lines at the end of a file. Please remove them and if your
editor is too stupid, then please pick a different editor.

Applying: Add PPP protocol support with HDLC framing
/data/devel/ofono/.git/rebase-apply/patch:166: new blank line at EOF.
+
/data/devel/ofono/.git/rebase-apply/patch:230: new blank line at EOF.
+
fatal: 2 lines add whitespace errors.

Before you submit any patches, you might wanna quickly check with git am
that they still apply. My .gitconfig uses a strict apply policy:

[diff]
	color = auto
	check = true
[apply]
	whitespace = error
[format-patch]
	check = true

Having diff and format-patch color your whitespace damages is always a
good idea. Then you see what is wrong.

Regards

Marcel



  reply	other threads:[~2010-03-20 15:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100319194705.214150215@linux.intel.com>
2010-03-19 19:46 ` [patch 1/6] Add PPP protocol support with HDLC framing Kristen Carlson Accardi
2010-03-20 15:33   ` Marcel Holtmann [this message]
2010-03-19 19:46 ` [patch 2/6] Generic PPP control protocol Kristen Carlson Accardi
2010-03-19 19:46 ` [patch 3/6] LCP support Kristen Carlson Accardi
2010-03-19 19:46 ` [patch 4/6] CHAP with MD5 authentication Kristen Carlson Accardi
2010-03-19 19:46 ` [patch 5/6] IP support for PPP Kristen Carlson Accardi
2010-03-19 19:46 ` [patch 6/6] Allow gsmdial to use gatchat ppp support Kristen Carlson Accardi
2010-03-20 15:35   ` Marcel Holtmann
     [not found] <20100317000824.420232401@linux.intel.com>
2010-03-17  0:13 ` [patch 1/6] Add PPP protocol support with HDLC framing Kristen Carlson Accardi
2010-03-17  6:28   ` Marcel Holtmann
     [not found] <20100311214022.838696145@linux.intel.com>
2010-03-11 22:00 ` kristen
2010-03-12  2:17   ` Denis Kenzior
2010-03-15 22:04     ` Kristen Carlson Accardi
2010-03-15 22:20       ` Denis Kenzior
2010-03-12  2:24   ` Denis Kenzior
2010-03-12  6:51     ` Marcel Holtmann

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=1269099212.2700.179.camel@localhost.localdomain \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox