From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>, Brian Norris <computersforpeace@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
Eva Rachel Retuya <eraretuya@gmail.com>
Subject: linux-next: manual merge of the staging tree with the l2-mtd tree
Date: Mon, 2 Nov 2015 00:35:53 +1100 [thread overview]
Message-ID: <20151102003553.75b8236d@canb.auug.org.au> (raw)
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in:
drivers/staging/mt29f_spinand/mt29f_spinand.c
between commit:
45aaeff94719 ("mtd: nand: pass page number to ecc->write_xxx() methods")
from the l2-mtd tree and commits:
74f63bd664b6 ("Staging: mt29f_spinand: Use preferred kernel types")
92fdd777976e ("Staging: mt29f_spinand: Indent to match open parenthesis")
from the staging tree.
I fixed it up (see below) and can carry the fix as necessary (no action
is required).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
diff --cc drivers/staging/mt29f_spinand/mt29f_spinand.c
index b2e6237ae913,20a3f8eeb264..000000000000
--- a/drivers/staging/mt29f_spinand/mt29f_spinand.c
+++ b/drivers/staging/mt29f_spinand/mt29f_spinand.c
@@@ -612,10 -612,10 +612,10 @@@ static int spinand_erase_block(struct s
#ifdef CONFIG_MTD_SPINAND_ONDIEECC
static int spinand_write_page_hwecc(struct mtd_info *mtd,
- struct nand_chip *chip, const uint8_t *buf, int oob_required,
- int page)
+ struct nand_chip *chip,
- const u8 *buf, int oob_required)
++ const u8 *buf, int oob_required, int page)
{
- const uint8_t *p = buf;
+ const u8 *p = buf;
int eccsize = chip->ecc.size;
int eccsteps = chip->ecc.steps;
next reply other threads:[~2015-11-01 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 13:35 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-28 6:54 linux-next: manual merge of the staging tree with the l2-mtd tree Stephen Rothwell
2011-12-28 8:54 ` Artem Bityutskiy
2011-12-28 9:04 ` Artem Bityutskiy
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=20151102003553.75b8236d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=eraretuya@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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