linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: "Ruslan V. Sushko" <rsushko@ru.mvista.com>, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH 3/3] ppc32: MTD support for Yucca board
Date: Mon, 21 Nov 2005 08:57:45 -0700	[thread overview]
Message-ID: <20051121085745.A19935@cox.net> (raw)
In-Reply-To: <4381E1A1.1060405@ru.mvista.com>; from vbordug@ru.mvista.com on Mon, Nov 21, 2005 at 06:02:57PM +0300

On Mon, Nov 21, 2005 at 06:02:57PM +0300, Vitaly Bordug wrote:
> Guess this should come through MTD community (linux-mtd@lists.infradead.org), rebased to 
> the MTD tree of course.

Indeed, however, it need to be split so the driver/mtd portion goes to
the MTD maintainers. The arch/ppc portion will go in through the powerpc
tree.

-Matt

      reply	other threads:[~2005-11-21 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 14:26 [PATCH 3/3] ppc32: MTD support for Yucca board Ruslan V. Sushko
2005-11-21 15:02 ` Vitaly Bordug
2005-11-21 15:57   ` Matt Porter [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=20051121085745.A19935@cox.net \
    --to=mporter@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rsushko@ru.mvista.com \
    --cc=vbordug@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).