From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
linux-mtd@lists.infradead.org,
David Woodhouse <David.Woodhouse@intel.com>
Subject: Re: [PATCH 1/3] mtd: bcm47xxsflash: store info about flash type
Date: Wed, 06 Mar 2013 11:23:51 +0200 [thread overview]
Message-ID: <1362561831.21850.26.camel@sauron> (raw)
In-Reply-To: <1361341929-11153-1-git-send-email-zajec5@gmail.com>
On Wed, 2013-02-20 at 07:32 +0100, Rafał Miłecki wrote:
> It's going to be needed for erase and write operations, they differ
> between Atmel and ST flashes.
>
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Aiaiai!
--------------------------------------------------------------------------------
Bisectability test results for configuration "mips-bcm47xx_defconfig,mips,mips-linux-"
Failed to build the following commit for configuration "mips-bcm47xx_defconfig"":
ab61426 mtd: bcm47xxsflash: store info about flash type
drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe':
drivers/mtd/devices/bcm47xxsflash.c:64:14: error: 'struct bcm47xxsflash' has no member named 'bcma_cc'
make[4]: *** [drivers/mtd/devices/bcm47xxsflash.o] Error 1
--------------------------------------------------------------------------------
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-03-06 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 6:32 [PATCH 1/3] mtd: bcm47xxsflash: store info about flash type Rafał Miłecki
2013-02-20 6:32 ` [PATCH 2/3] mtd: bcm47xxsflash: keep a reference to the BCMA ChipCommon Rafał Miłecki
2013-02-20 6:32 ` [PATCH 3/3] mtd: bcm47xxsflash: define opcodes Rafał Miłecki
2013-03-06 9:23 ` Artem Bityutskiy [this message]
2013-03-06 10:39 ` [PATCH 1/3] mtd: bcm47xxsflash: store info about flash type Rafał Miłecki
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=1362561831.21850.26.camel@sauron \
--to=dedekind1@gmail.com \
--cc=David.Woodhouse@intel.com \
--cc=hauke@hauke-m.de \
--cc=linux-mtd@lists.infradead.org \
--cc=zajec5@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