From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Brian Norris <computersforpeace@gmail•com>,
Kalle Valo <kvalo@codeaurora•org>,
linux-wireless@vger•kernel.org
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
"Rafał Miłecki" <zajec5@gmail•com>
Subject: linux-next: manual merge of the l2-mtd tree with the wireless-drivers-next tree
Date: Wed, 20 Jul 2016 12:31:33 +1000 [thread overview]
Message-ID: <20160720123133.44dab209@canb.auug.org.au> (raw)
Hi Brian,
Today's linux-next merge of the l2-mtd tree got a conflict in:
drivers/mtd/devices/Kconfig
between commit:
efacc699139e ("mtd: add arch dependency for MTD_BCM47XXSFLASH symbol")
from the wireless-drivers-next tree and commit:
0a526341fee0 ("mtd: update description of MTD_BCM47XXSFLASH symbol")
from the l2-mtd tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc drivers/mtd/devices/Kconfig
index 64a248556d29,bf8238fb2e12..000000000000
--- a/drivers/mtd/devices/Kconfig
+++ b/drivers/mtd/devices/Kconfig
@@@ -113,8 -113,8 +113,8 @@@ config MTD_SST25
if you want to specify device partitioning.
config MTD_BCM47XXSFLASH
- tristate "R/O support for serial flash on BCMA bus"
+ tristate "Support for serial flash on BCMA bus"
- depends on BCMA_SFLASH
+ depends on BCMA_SFLASH && (MIPS || ARM)
help
BCMA bus can have various flash memories attached, they are
registered by bcma as platform devices. This enables driver for
reply other threads:[~2016-07-20 2:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160720123133.44dab209@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=computersforpeace@gmail$(echo .)com \
--cc=kvalo@codeaurora$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=zajec5@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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