From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
Alexander Shiyan <shc_work@mail.ru>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Subject: Re: [PATCH 1/4] mtd: nand: gpio: Determine bus width automatically
Date: Sun, 28 Jul 2013 19:53:00 -0300 [thread overview]
Message-ID: <20130728225259.GA4215@localhost> (raw)
In-Reply-To: <CAN8TOE8_K3rT5gLFBGOnghK-ajFcjQK22mm0qYmF+hSvkT27aA@mail.gmail.com>
On Tue, Jul 23, 2013 at 11:42:08PM -0700, Brian Norris wrote:
> On Tue, Jul 23, 2013 at 5:28 AM, Alexander Shiyan <shc_work@mail.ru> wrote:
> > This patch provide automatically determine of bus width. If resource size,
> > supplied to the driver more than 1 byte, the NAND_BUSWIDTH_AUTO option
> > will be used in the MTD core.
>
> I presume this depends on the bugfix I sent for NAND_BUSWIDTH_AUTO /
> nand_set_defaults()? That's worth noting (as I am right now), for
> whenever someone gets around to merging this.
>
> > Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
> > ---
> > .../devicetree/bindings/mtd/gpio-control-nand.txt | 5 ++---
>
> Considering the changes in device-tree bindings, it's good to CC the
> device-tree list, I believe.
>
Adding the new devicetree list in Cc.
Keep in mind you might want to split the DT binding part of the patch
into a separate patch. For small patches like this one, it's probably
not a big deal.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Alexander Shiyan <shc_work@mail.ru>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/4] mtd: nand: gpio: Determine bus width automatically
Date: Sun, 28 Jul 2013 19:53:00 -0300 [thread overview]
Message-ID: <20130728225259.GA4215@localhost> (raw)
In-Reply-To: <CAN8TOE8_K3rT5gLFBGOnghK-ajFcjQK22mm0qYmF+hSvkT27aA@mail.gmail.com>
On Tue, Jul 23, 2013 at 11:42:08PM -0700, Brian Norris wrote:
> On Tue, Jul 23, 2013 at 5:28 AM, Alexander Shiyan <shc_work@mail.ru> wrote:
> > This patch provide automatically determine of bus width. If resource size,
> > supplied to the driver more than 1 byte, the NAND_BUSWIDTH_AUTO option
> > will be used in the MTD core.
>
> I presume this depends on the bugfix I sent for NAND_BUSWIDTH_AUTO /
> nand_set_defaults()? That's worth noting (as I am right now), for
> whenever someone gets around to merging this.
>
> > Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
> > ---
> > .../devicetree/bindings/mtd/gpio-control-nand.txt | 5 ++---
>
> Considering the changes in device-tree bindings, it's good to CC the
> device-tree list, I believe.
>
Adding the new devicetree list in Cc.
Keep in mind you might want to split the DT binding part of the patch
into a separate patch. For small patches like this one, it's probably
not a big deal.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-07-28 22:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 12:28 [PATCH 1/4] mtd: nand: gpio: Determine bus width automatically Alexander Shiyan
2013-07-23 12:28 ` [PATCH 2/4] mtd: nand: gpio: Use devm_gpio_request_one() where possible Alexander Shiyan
2013-07-23 12:28 ` [PATCH 3/4] mtd: nand: gpio: Return real nand_scan() error code on fail and simplify error path Alexander Shiyan
2013-07-23 12:28 ` [PATCH 4/4] mtd: nand: gpio: Add support for multichip devices Alexander Shiyan
2013-07-24 6:42 ` [PATCH 1/4] mtd: nand: gpio: Determine bus width automatically Brian Norris
2013-07-24 6:42 ` Brian Norris
2013-07-24 6:52 ` Brian Norris
2013-07-24 6:52 ` Brian Norris
2013-07-24 7:02 ` Brian Norris
2013-07-24 7:02 ` Brian Norris
2013-07-24 13:28 ` Alexander Shiyan
2013-07-24 13:28 ` Alexander Shiyan
2013-07-27 20:50 ` Brian Norris
2013-07-27 20:50 ` Brian Norris
2013-07-27 20:58 ` Brian Norris
2013-07-27 20:58 ` Brian Norris
2013-07-28 22:53 ` Ezequiel Garcia [this message]
2013-07-28 22:53 ` Ezequiel Garcia
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=20130728225259.GA4215@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shc_work@mail.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.