All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Atsushi Nemoto" <anemo@mba.ocn.ne.jp>
Cc: linux-mtd@lists.infradead.org, vapier@gentoo.org,
	dwmw2@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: unify mtd partition/device registration
Date: Thu, 13 Nov 2008 09:47:00 -0500	[thread overview]
Message-ID: <8bd0f97a0811130647qeb5aea4tdc115f283bc352d@mail.gmail.com> (raw)
In-Reply-To: <20081113.224350.18312549.anemo@mba.ocn.ne.jp>

On Thu, Nov 13, 2008 at 08:43, Atsushi Nemoto wrote:
> On Wed, 12 Nov 2008 18:38:53 -0500, Mike Frysinger wrote:
>> +int parse_mtd(struct mtd_info *mtd, const char **probe_types,
>> +              struct mtd_partition *parts, int nr_parts)
>> +{
>> +#ifdef CONFIG_MTD_PARTITIONS
>> +     const char *default_part_probe_types[] = {
>> +             "cmdlinepart",
>> +             "RedBoot",
>> +             NULL
>> +     };
>
> But I'm not sure this default_part_probe_types is appropriate.
>
> How about enclose each parser with #ifdefs?
>
>        const char *default_part_probe_types[] = {
> #ifdef CONFIG_MTD_CMDLINE_PARTS
>                "cmdlinepart",
> #endif
> #ifdef CONFIG_MTD_REDBOOT_PARTS
>                "RedBoot",
> #endif
>                NULL
>        };
>
> This get rid of "RedBoot partition parsing not available" noise in
> boot message when you use default_part_probe_types without
> MTD_REDBOOT_PARTS.

yeah, that parsing thing is annoying, but i didnt think enough so to
add ifdef's.  i'm fine with it either way.
-mike

WARNING: multiple messages have this Message-ID (diff)
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Atsushi Nemoto" <anemo@mba.ocn.ne.jp>
Cc: vapier@gentoo.org, linux-mtd@lists.infradead.org,
	dwmw2@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: unify mtd partition/device registration
Date: Thu, 13 Nov 2008 09:47:00 -0500	[thread overview]
Message-ID: <8bd0f97a0811130647qeb5aea4tdc115f283bc352d@mail.gmail.com> (raw)
In-Reply-To: <20081113.224350.18312549.anemo@mba.ocn.ne.jp>

On Thu, Nov 13, 2008 at 08:43, Atsushi Nemoto wrote:
> On Wed, 12 Nov 2008 18:38:53 -0500, Mike Frysinger wrote:
>> +int parse_mtd(struct mtd_info *mtd, const char **probe_types,
>> +              struct mtd_partition *parts, int nr_parts)
>> +{
>> +#ifdef CONFIG_MTD_PARTITIONS
>> +     const char *default_part_probe_types[] = {
>> +             "cmdlinepart",
>> +             "RedBoot",
>> +             NULL
>> +     };
>
> But I'm not sure this default_part_probe_types is appropriate.
>
> How about enclose each parser with #ifdefs?
>
>        const char *default_part_probe_types[] = {
> #ifdef CONFIG_MTD_CMDLINE_PARTS
>                "cmdlinepart",
> #endif
> #ifdef CONFIG_MTD_REDBOOT_PARTS
>                "RedBoot",
> #endif
>                NULL
>        };
>
> This get rid of "RedBoot partition parsing not available" noise in
> boot message when you use default_part_probe_types without
> MTD_REDBOOT_PARTS.

yeah, that parsing thing is annoying, but i didnt think enough so to
add ifdef's.  i'm fine with it either way.
-mike

  parent reply	other threads:[~2008-11-13 14:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 23:38 [PATCH] mtd: unify mtd partition/device registration Mike Frysinger
2008-11-12 23:39 ` [PATCH] mtd/physmap: use parse_mtd() Mike Frysinger
2008-11-13 13:51   ` Atsushi Nemoto
2008-11-13 13:51     ` Atsushi Nemoto
2008-11-13 14:44     ` Mike Frysinger
2008-11-13 14:44       ` Mike Frysinger
2008-11-14 21:41   ` Andrew Morton
2008-11-14 21:41     ` Andrew Morton
2008-11-14 22:07     ` Mike Frysinger
2008-11-14 22:07       ` Mike Frysinger
2008-11-12 23:39 ` [PATCH] mtd/bfin-async-flash: " Mike Frysinger
2008-11-13 13:43 ` [PATCH] mtd: unify mtd partition/device registration Atsushi Nemoto
2008-11-13 13:43   ` Atsushi Nemoto
2008-11-13 14:28   ` Atsushi Nemoto
2008-11-13 14:28     ` Atsushi Nemoto
2008-11-13 14:51     ` Mike Frysinger
2008-11-13 14:51       ` Mike Frysinger
2008-11-13 15:51       ` Atsushi Nemoto
2008-11-13 15:51         ` Atsushi Nemoto
2008-11-13 15:55         ` Mike Frysinger
2008-11-13 15:55           ` Mike Frysinger
2008-11-13 14:47   ` Mike Frysinger [this message]
2008-11-13 14:47     ` Mike Frysinger
2008-11-14 21:39 ` Andrew Morton
2008-11-14 21:39   ` Andrew Morton
2008-11-16 17:34 ` Jörn Engel
2008-11-16 17:34   ` Jörn Engel
2008-11-16 17:55   ` Mike Frysinger
2008-11-16 17:55     ` Mike Frysinger
2008-11-16 18:02     ` Jörn Engel
2008-11-16 18:02       ` Jörn Engel

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=8bd0f97a0811130647qeb5aea4tdc115f283bc352d@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vapier@gentoo.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.