From: Brian Norris <computersforpeace@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linux-mtd@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
Jaiprakash Singh <b44839@freescale.com>
Subject: Re: [PATCH v5 RESEND] IFC: Change IO accessor based on endianness
Date: Thu, 6 Aug 2015 16:44:50 -0700 [thread overview]
Message-ID: <20150806234450.GU10676@google.com> (raw)
In-Reply-To: <1438903478.2097.196.camel@freescale.com>
On Thu, Aug 06, 2015 at 06:24:38PM -0500, Scott Wood wrote:
> On Thu, 2015-08-06 at 09:52 -0700, Brian Norris wrote:
> > Who takes patches for drivers/memory/ again? I can take it via MTD if
> > no one else steps up.
> There's no maintainer listed. IIRC, when we previously discussed the patch
> we both said that it could go via either of our trees. I'll take it via mine.
I recall the conversation. I was just confused (again) by there being no
maintainer entry. Have at it.
> > It's nothing new, but this patch continues the pattern of using a global
> > pointer to the IFC device structure. Not pretty, but not worth holding
> > this up over.
>
> It's not pretty, but I see little reason to come up with more complicated
> infrastructure for the drivers finding each other given the low odds of ever
> seeing a single-kernel system with more than one IFC. It's impossible with
> current chips. If it ever does happen we can do something fancier.
Yep, I figured as much.
Brian
prev parent reply other threads:[~2015-08-06 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 2:17 [PATCH v5 RESEND] IFC: Change IO accessor based on endianness Scott Wood
2015-05-28 1:19 ` [v5,RESEND] " Scott Wood
2015-08-04 20:37 ` Scott Wood
2015-08-06 16:52 ` [PATCH v5 RESEND] " Brian Norris
2015-08-06 23:24 ` Scott Wood
2015-08-06 23:44 ` Brian Norris [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=20150806234450.GU10676@google.com \
--to=computersforpeace@gmail.com \
--cc=b44839@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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).