mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 1/2] ramoops: allow to build without OFTREE support
Date: Thu, 11 Feb 2016 10:33:55 +0100	[thread overview]
Message-ID: <1455183236-25952-1-git-send-email-l.stach@pengutronix.de> (raw)

Ramoops may be useful even without oftree support, as kernels
booted without a DT may have other means to reserve the
ramoops memory.

Fixes:
In function `ramoops_probe':
undefined reference to `of_add_reserve_entry'

Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
 fs/pstore/ram.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
index 66b4975a3035..fdd92a60a57a 100644
--- a/fs/pstore/ram.c
+++ b/fs/pstore/ram.c
@@ -455,7 +455,8 @@ static int ramoops_probe(struct ramoops_platform_data *pdata)
 		  ramoops_ecc);
 	globalvar_add_simple("linux.bootargs.ramoops", kernelargs);
 
-	of_add_reserve_entry(cxt->phys_addr, cxt->phys_addr + mem_size);
+	if (IS_ENABLED(CONFIG_OFTREE))
+		of_add_reserve_entry(cxt->phys_addr, cxt->phys_addr + mem_size);
 
 	return 0;
 
-- 
2.1.4


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2016-02-11  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11  9:33 Lucas Stach [this message]
2016-02-11  9:33 ` [PATCH 2/2] ratp-console: select CRC16 and POLLER, depend on CONSOLE_FULL Lucas Stach
2016-02-11 12:56 ` [PATCH 1/2] ramoops: allow to build without OFTREE support Sascha Hauer

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=1455183236-25952-1-git-send-email-l.stach@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=barebox@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