linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Michal Suchanek <hramrach@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Boris BREZILLON <b.brezillon.dev@gmail.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Petros Angelatos <petrosagg@gmail.com>,
	Michal Suchanek <hramrach@gmail.com>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Subject: [PATCH 0/2] New NAND chip IDs
Date: Tue, 28 Jul 2015 16:29:18 +0200	[thread overview]
Message-ID: <cover.1438093758.git.hramrach@gmail.com> (raw)

Hello,

the NAND chips on Cubietech boards are not known to Linux.

I used Petros Angelatos' patch from sunxi experimental tree for one chip and
added another chip.

I hope it's ok to send both patches to avoid merge conflict.

Thanks

Michal

Michal Suchanek (1):
  mtd: nand: add Samsung K9GBG08U0A chip id

Petros Angelatos (1):
  mtd: nand: add Samsung's K9GBG08U0B to nand_ids table

 drivers/mtd/nand/nand_ids.c | 6 ++++++
 1 file changed, 6 insertions(+)

-- 
2.1.4

             reply	other threads:[~2015-07-28 14:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 14:29 Michal Suchanek [this message]
2015-07-28 14:38 ` [PATCH 1/2] mtd: nand: add Samsung's K9GBG08U0B to nand_ids table Michal Suchanek
2015-07-28 14:38 ` [PATCH 2/2] mtd: nand: add Samsung K9GBG08U0A chip id Michal Suchanek
2015-07-28 14:49 ` [PATCH 0/2] New NAND chip IDs Hans de Goede
2015-07-28 15:10   ` Boris Brezillon
2015-07-28 15:13     ` Boris Brezillon
2015-07-28 15:16     ` Hans de Goede
2015-07-28 15:19   ` Boris Brezillon
2015-07-28 15:30     ` Boris Brezillon
2015-07-28 15:32       ` Hans de Goede

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=cover.1438093758.git.hramrach@gmail.com \
    --to=hramrach@gmail.com \
    --cc=b.brezillon.dev@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=petrosagg@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).