linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Jiancheng Xue <xuejiancheng@hisilicon.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mtd@lists.infradead.org, ezequiel@vanguardiasur.com.ar,
	jteki@openedev.com, cyrille.pitchen@atmel.com,
	robh+dt@kernel.org, yanhaifeng@hisilicon.com,
	yanghongwei@hisilicon.com, linshunquan1@hisilicon.com,
	Binquan Peng <pengbinquan@hisilicon.com>
Subject: Re: [PATCH v12] mtd: spi-nor: add hisilicon spi-nor flash controller driver
Date: Thu, 14 Jul 2016 19:21:13 -0700	[thread overview]
Message-ID: <20160715022113.GA144623@google.com> (raw)
In-Reply-To: <57883BC5.7060600@hisilicon.com>

On Fri, Jul 15, 2016 at 09:26:29AM +0800, Jiancheng Xue wrote:
> On 2016/7/14 9:13, Brian Norris wrote:
> > Pushed to l2-mtd.git, with the following diff due to API changes. Please
> > review to be sure it looks OK to you.
> > 
> 
> The changes are OK to me. Thanks!

Thanks for double checking.

> > Also, please base changes on l2-mtd.git or linux-next.git in the future.
> > 
> 
> The l2-mtd.git can't be accessed through http protocol now. The git protocol
> is forbidden in our office.

Hmm, that's too bad. I could probably bug the infradead.org admin to
change that...

At worst, you can at least check out the gitweb. e.g.:

http://git.infradead.org/l2-mtd.git/commitdiff/e523f11141bdc24f65775f0b1fa4a7ed404e68cc

> I will generate patch based on linux-next.git.

That will usually work just fine too. Although there can be some small
delay between linux-next updates (ranging from about a day, up to a week
or two (?) around the merge window).

Regards,
Brian

      reply	other threads:[~2016-07-15  2:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  7:48 [PATCH v12] mtd: spi-nor: add hisilicon spi-nor flash controller driver Jiancheng Xue
2016-07-14  1:13 ` Brian Norris
2016-07-15  1:26   ` Jiancheng Xue
2016-07-15  2:21     ` 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=20160715022113.GA144623@google.com \
    --to=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@atmel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=jteki@openedev.com \
    --cc=linshunquan1@hisilicon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pengbinquan@hisilicon.com \
    --cc=robh+dt@kernel.org \
    --cc=xuejiancheng@hisilicon.com \
    --cc=yanghongwei@hisilicon.com \
    --cc=yanhaifeng@hisilicon.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).