public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <oss@buserror.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/7] mtd: nand: Add+use mtd_to/from_nand and nand_get/set_controller_data
Date: Wed, 15 Jun 2016 12:39:50 -0500	[thread overview]
Message-ID: <1466012390.22191.173.camel@buserror.net> (raw)
In-Reply-To: <20160615100729.0aa3fbb8@bbrezillon>

On Wed, 2016-06-15 at 10:07 +0200, Boris Brezillon wrote:
> On Wed, 15 Jun 2016 09:59:15 +0200
> Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
> 
> > Hi Scott,
> > 
> > On Thu, 09 Jun 2016 21:07:00 -0500
> > Scott Wood <oss@buserror.net> wrote:
> > 
> > > On Mon, 2016-06-06 at 18:02 +0200, Boris Brezillon wrote:  
> > > > On Mon, 30 May 2016 13:57:56 -0500
> > > > Scott Wood <oss@buserror.net> wrote:
> > > >     
> > > > > These functions are part of the Linux 4.6 sync.  They are being
> > > > > added
> > > > > before the main sync patch in order to make it easier to address the
> > > > > issue across all NAND drivers (many/most of which do not closely
> > > > > track
> > > > > their Linux counterparts) separately from other merge issues.    
> > > > 
> > > > Some drivers are still directly accessing chip->mtd. Here is a patch
> > > > fixing those places [1] (not tested).
> > > > 
> > > > [1] http://code.bulix.org/inu69a-100476????;
> > > 
> > > Could you send this as a proper patch?  
> > 
> > Sure, see below. You can squash the changes into you patch (hence the
> > !fixup prefix).
> 
> Oops, sorry this version was buggy: mtd_to_nand() was called instead of
> nand_to_mtd() in a few places. Here is an updated one.
> 
> --->8---
> From 9c885ff8b3d96f29dfa5ef9850c4519a88a7912d Mon Sep 17 00:00:00 2001
> From: Boris Brezillon <boris.brezillon@free-electrons.com>
> Date: Wed, 15 Jun 2016 09:48:48 +0200
> Subject: [PATCH] fixup! mtd: nand: Add+use mtd_to/from_nand and
>  nand_get/set_controller_data

It's too late to amend the commit.  I need a standalone patch with signoff,
etc.

-Scott

  reply	other threads:[~2016-06-15 17:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 18:57 [U-Boot] [PATCH 1/7] mtd: nand: Remove jz4740 driver Scott Wood
2016-05-30 18:57 ` [U-Boot] [PATCH 2/7] mtd: nand: Remove docg4 driver and palmtreo680 flashing tool Scott Wood
2016-05-30 18:57 ` [U-Boot] [PATCH 3/7] mtd: nand: Remove nand_info_t typedef Scott Wood
2016-05-30 18:57 ` [U-Boot] [PATCH 4/7] nand: Embed mtd_info in struct nand_chip Scott Wood
2016-05-30 18:57 ` [U-Boot] [PATCH 5/7] mtd: nand: Add+use mtd_to/from_nand and nand_get/set_controller_data Scott Wood
2016-06-06 16:02   ` Boris Brezillon
2016-06-10  2:07     ` Scott Wood
2016-06-15  7:59       ` Boris Brezillon
2016-06-15  8:07         ` Boris Brezillon
2016-06-15 17:39           ` Scott Wood [this message]
2016-06-15 18:38             ` Boris Brezillon
2016-05-30 18:57 ` [U-Boot] [PATCH 6/7] mtd: nand: Add page argument to write_page() etc Scott Wood
2016-05-30 18:57 ` [U-Boot] [PATCH 7/7] mtd: nand: Sync with Linux v4.6 Scott Wood
2016-05-31  6:48   ` Heiko Schocher
2016-05-31  7:19     ` Scott Wood
2016-05-31  7:10   ` Boris Brezillon
2016-06-06 16:04   ` Boris Brezillon
2016-06-07  4:20     ` Heiko Schocher

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=1466012390.22191.173.camel@buserror.net \
    --to=oss@buserror.net \
    --cc=u-boot@lists.denx.de \
    /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