All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] extend physmap.c to support run-time configure and partitioning (take 3)
Date: Wed, 5 Nov 2003 09:56:58 -0800	[thread overview]
Message-ID: <20031105095658.B19785@mvista.com> (raw)
In-Reply-To: <1068023691.6065.7.camel@hades.cambridge.redhat.com>; from dwmw2@infradead.org on Wed, Nov 05, 2003 at 09:14:51AM +0000

On Wed, Nov 05, 2003 at 09:14:51AM +0000, David Woodhouse wrote:
> On Tue, 2003-11-04 at 16:44 -0800, Jun Sun wrote:
> > David,
> > 
> > Since you did not give any preference on how board should
> > pass partition info to physmap, I just picked a reasonable
> > one.
> 
> Sorry for the lack of response. Been beating up JFFS2 with LTP and it's
> been, erm, 'interesting'. S'fixed now though :)
> 
> > Is this patch now good enough to apply?  Thanks.
> 
> I'd still prefer to do it without any static variables in physmap.c. 
> 

Hmm, can you be more specific?  Here are all static variables that
matter in physmap.c.  Which ones are you thinking to eliminate?  And in 
what way?  (Assuming you do not mean I just drop "static" modifier...)

static struct mtd_info *mymtd;

static struct mtd_partition *mtd_parts;
static int                   mtd_parts_nb;

static int num_physmap_partitions;
static struct mtd_partition *physmap_partitions;

Jun

  reply	other threads:[~2003-11-05 17:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05  0:44 [PATCH] extend physmap.c to support run-time configure and partitioning (take 3) Jun Sun
2003-11-05  9:14 ` David Woodhouse
2003-11-05 17:56   ` Jun Sun [this message]
2003-11-06  9:50     ` David Woodhouse
2003-11-06 19:09       ` Jun Sun
2003-11-10 23:19         ` Jun Sun

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=20031105095658.B19785@mvista.com \
    --to=jsun@mvista.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.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.