From: Artem Bityutskiy <dedekind1@gmail.com>
To: Andres Salomon <dilinger@queued.net>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 09/17] t7166xb: mfd_cell is now implicitly available to drivers
Date: Mon, 14 Feb 2011 13:04:51 +0200 [thread overview]
Message-ID: <1297681491.2854.19.camel@localhost> (raw)
In-Reply-To: <20110214020028.2449dbe4@debxo>
On Mon, 2011-02-14 at 02:00 -0800, Andres Salomon wrote:
> On Mon, 14 Feb 2011 11:17:44 +0200
> Artem Bityutskiy <dedekind1@gmail.com> wrote:
>
> > On Fri, 2011-02-11 at 18:11 -0800, Andres Salomon wrote:
> > > No need to explicitly set the cell's platform_data/data_size.
> > >
> > > Modify clients to use mfd_get_cell helper function instead of
> > > accessing platform_data directly.
> >
> > Wold it be possible to separate out MTD-related changes?
> >
>
> It's possible, sure. Patch 09 is the only one that touches
> drivers/mtd. It would introduce build and/or runtime problems if mtd
> and mfd trees get out of synch, however.
>
> I was hoping to get subsystem maintainer ACKs and run everything
> through the mfd tree, if possible (though I haven't heard any feedback
> from Samuel about any of this yet).
OK, I'm not MTD maintainer, but I'd say that you can merge it via mfd
tree. I did no look at the whole set, but mtd changes look trivial and
there should not be issues with merging that via the mfd tree.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-02-14 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 2:11 [PATCH 09/17] t7166xb: mfd_cell is now implicitly available to drivers Andres Salomon
2011-02-14 9:17 ` Artem Bityutskiy
2011-02-14 10:00 ` Andres Salomon
2011-02-14 11:04 ` Artem Bityutskiy [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=1297681491.2854.19.camel@localhost \
--to=dedekind1@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dilinger@queued.net \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sameo@linux.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