All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [STABLE][PATCH] recipes/unifdef/files/unifdef.c : more modern glibc expose getline from
Date: Thu, 07 May 2009 10:10:55 +0200	[thread overview]
Message-ID: <gtu527$coc$1@ger.gmane.org> (raw)
In-Reply-To: <1240929390-16041-1-git-send-email-k.kooi@student.utwente.nl>

ping

On 28-04-09 16:36, Koen Kooi wrote:
> From: Graeme Gregory<dp@xora.org.uk>
>
>
> Signed-off-by: Koen Kooi<koen@openembedded.org>
> ---
>   recipes/unifdef/files/unifdef.c |    6 +++---
>   1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/recipes/unifdef/files/unifdef.c b/recipes/unifdef/files/unifdef.c
> index 552025e..977e682 100644
> --- a/recipes/unifdef/files/unifdef.c
> +++ b/recipes/unifdef/files/unifdef.c
> @@ -206,7 +206,7 @@ static void             done(void);
>   static void             error(const char *);
>   static int              findsym(const char *);
>   static void             flushline(bool);
> -static Linetype         getline(void);
> +static Linetype         parseline(void);
>   static Linetype         ifeval(const char **);
>   static void             ignoreoff(void);
>   static void             ignoreon(void);
> @@ -512,7 +512,7 @@ process(void)
>
>   	for (;;) {
>   		linenum++;
> -		lineval = getline();
> +		lineval = parseline();
>   		trans_table[ifstate[depth]][lineval]();
>   		debug("process %s ->  %s depth %d",
>   		    linetype_name[lineval],
> @@ -526,7 +526,7 @@ process(void)
>    * help from skipcomment().
>    */
>   static Linetype
> -getline(void)
> +parseline(void)
>   {
>   	const char *cp;
>   	int cursym;





  reply	other threads:[~2009-05-07  8:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 14:36 [STABLE][PATCH] recipes/unifdef/files/unifdef.c : more modern glibc expose getline from Koen Kooi
2009-05-07  8:10 ` Koen Kooi [this message]
2009-05-07  8:11 ` Koen Kooi
2009-05-07 12:20   ` Philip Balister

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='gtu527$coc$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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.