public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Shaohua Li <shaohua.li@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: [patch]fastboot: remove duplicate unpack_to_rootfs()
Date: Wed, 13 Aug 2008 09:52:36 +0200	[thread overview]
Message-ID: <20080813075236.GA8052@elte.hu> (raw)
In-Reply-To: <20080813074503.GB398@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> the dry_run variable is now unused in unpack_to_rootfs() and could be 
> eliminated.

also, while we are materially touching init/initramfs.c, that file has 
collected a few uglies in the past few years, checkpatch --file says:

  total: 7 errors, 7 warnings, 3 checks, 562 lines checked

it has a few other problems as well that can be seen if you look at the 
file. Unused macros:

 /* Diagnostic functions (stubbed out) */
 #define Assert(cond,msg)
 #define Trace(x)
 #define Tracev(x)
 #define Tracevv(x)
 #define Tracec(c,x)
 #define Tracecv(c,x)

 #define STATIC static
 #define INIT __init

lots of no-newline-after-variable-definitions instances:

 {
         int written;
         dry_run = check_only;

no-newline-before-return:

         kfree(header_buf);
         return message;
 }

so it would be nice to start off with a cleanup [strictly no code 
changed] patch.

then it also has an absolutely crazy turn-error-printouts-off hack:

 static __initdata char *message;
 static void __init error(char *x)
 {
         if (!message)
                 message = x;
 }

which is unobvious, 100% unused and should be removed.

those error()s should be pr_debug() perhaps. [this should be a second 
cleanup patch as it changes the code]

Hm?

	Ingo

  reply	other threads:[~2008-08-13  7:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13  6:07 [patch]fastboot: remove duplicate unpack_to_rootfs() Shaohua Li
2008-08-13  7:45 ` Ingo Molnar
2008-08-13  7:52   ` Ingo Molnar [this message]
2008-08-13  8:06     ` Andrew Morton
2008-08-13  9:14       ` Ingo Molnar
2008-08-13  8:11     ` Frans Meulenbroeks
2008-08-13  9:15       ` Ingo Molnar
2008-08-13  8:00   ` Li, Shaohua
2008-08-13  9:26   ` Li, Shaohua
  -- strict thread matches above, loose matches on Subject: below --
2009-03-15 18:23 [2.6.30] What's in the async boot tree Arjan van de Ven
2009-03-15 18:25 ` [PATCH] fastboot: remove duplicate unpack_to_rootfs() Arjan van de Ven

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=20080813075236.GA8052@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    /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