linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Ben Dooks <ben-linux@fluff.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtdcore.c: share syms with mtd_blkdev.c
Date: Tue, 29 May 2007 10:42:32 -0500	[thread overview]
Message-ID: <1180453352.3360.56.camel@zod.rchland.ibm.com> (raw)
In-Reply-To: <20070528192834.GA13509@fluff.org.uk>

On Mon, 2007-05-28 at 20:28 +0100, Ben Dooks wrote:
> Fix the sparse warnings generated by the implicit
> dependency of mtd_blkdevs.c and mtd_core.c for the
> two symbols mtd_table and mtd_table_mutex. This is
> done by adding an local header file mtdcore.h to
> define these (including the warning about the
> non-proliferation of these symbols).

Looks good.

josh

      reply	other threads:[~2007-05-29 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28 19:28 [PATCH] mtdcore.c: share syms with mtd_blkdev.c Ben Dooks
2007-05-29 15:42 ` Josh Boyer [this message]

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=1180453352.3360.56.camel@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=ben-linux@fluff.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).