From: Brian Norris <computersforpeace@gmail.com>
To: linux-mtd@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>, "Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>
Subject: Re: [PATCH 1/3] mtd: brcmnand: refactor bcm63138 SoC layering
Date: Wed, 30 Sep 2015 13:08:39 -0700 [thread overview]
Message-ID: <20150930200839.GI143959@google.com> (raw)
In-Reply-To: <1432166706-4320-1-git-send-email-computersforpeace@gmail.com>
On Wed, May 20, 2015 at 05:05:04PM -0700, Brian Norris wrote:
> Removes an unnecessary allocation and saves a little bit of pointer
> chasing.
>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Pushed these 3 to l2-mtd.git
prev parent reply other threads:[~2015-09-30 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 0:05 [PATCH 1/3] mtd: brcmnand: refactor bcm63138 SoC layering Brian Norris
2015-05-21 0:05 ` [PATCH 2/3] mtd: brcmnand: refactor iProc " Brian Norris
2015-05-21 0:05 ` [PATCH 3/3] mtd: brcmnand: remove unnecessary fields from brcmnand_soc Brian Norris
2015-09-30 20:08 ` 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=20150930200839.GI143959@google.com \
--to=computersforpeace@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=linux-mtd@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=zajec5@gmail.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).