From: Randy Dunlap <randy.dunlap@oracle.com>
To: Alexey Korolev <akorolev@infradead.org>
Cc: Alexander Beregalov <a.beregalov@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: mtd/lpddr/qinfo_probe.c needs lpddr_cmds to be compiled
Date: Sun, 11 Jan 2009 08:51:56 -0800 [thread overview]
Message-ID: <496A23AC.1090909@oracle.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0901110958360.20119@casper.infradead.org>
Alexey Korolev wrote:
> Hi Randy,
>
> I've just checked 2.6.29-rc1. It contains LPDDR patches but does not contain this patch.
> Do you know whom I should ask to make this included?
MAINTAINERS file:
MEMORY TECHNOLOGY DEVICES (MTD)
P: David Woodhouse
M: dwmw2@infradead.org
> Thanks,
> Alexey
>
>>> drivers/built-in.o: In function `lpddr_probe':
>>> drivers/mtd/lpddr/qinfo_probe.c:215:
>>> undefined reference to `lpddr_cmdset'
>>>
>>> # CONFIG_MTD_LPDDR is not set
>>> CONFIG_MTD_QINFO_PROBE=y
>>> --
>> This patch has been posted, just needs to be merged (hint):
>> ---
>>
>>
>> Signed-off-by: Alexey Korolev <akorolev@infradead.org>
>> ---
>> diff --git a/drivers/mtd/lpddr/Kconfig b/drivers/mtd/lpddr/Kconfig
>> index acd4ea9..5a401d8 100644
>> --- a/drivers/mtd/lpddr/Kconfig
>> +++ b/drivers/mtd/lpddr/Kconfig
>> @@ -12,6 +12,7 @@ config MTD_LPDDR
>> DDR memories, intended for battery-operated systems.
>>
>> config MTD_QINFO_PROBE
>> + depends on MTD_LPDDR
>> tristate "Detect flash chips by QINFO probe"
>> help
>> Device Information for LPDDR chips is offered through the Overlay
>>
>>
--
~Randy
next prev parent reply other threads:[~2009-01-11 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 2:16 mtd/lpddr/qinfo_probe.c needs lpddr_cmds to be compiled Alexander Beregalov
2009-01-10 5:16 ` Randy Dunlap
2009-01-11 10:03 ` Alexey Korolev
2009-01-11 16:51 ` Randy Dunlap [this message]
2009-01-11 18:16 ` Alexey Korolev
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=496A23AC.1090909@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=a.beregalov@gmail.com \
--cc=akorolev@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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