From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] Fix drivers/memory O= build
Date: Tue, 10 Apr 2018 06:55:16 -0700 [thread overview]
Message-ID: <20180410135516.GT5700@atomide.com> (raw)
In-Reply-To: <ba6087c5-c69e-1adc-9d9d-0ef5b19fb30e@ti.com>
* Dave Gerlach <d-gerlach@ti.com> [180409 16:07]:
> I've inlined the changes below. I will send a proper split up series if it's
> considered acceptable.
Seems fine from my point of view. No need to split the patch, best to
do the fix as a single patch.
We should test build it also with make randconfigs though.
So assuming others are OK with this and it does not introduce
new randconfig build errors:
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2018-04-10 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 10:25 [BUG] Fix drivers/memory O= build Russell King - ARM Linux
2018-04-06 16:46 ` Tony Lindgren
2018-04-06 18:45 ` Santosh Shilimkar
2018-04-06 18:55 ` Russell King - ARM Linux
2018-04-07 2:55 ` Masahiro Yamada
2018-04-07 13:38 ` Russell King - ARM Linux
2018-04-09 16:05 ` Dave Gerlach
2018-04-10 13:55 ` Tony Lindgren [this message]
2018-04-10 15:01 ` Masahiro Yamada
2018-04-11 21:17 ` Dave Gerlach
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=20180410135516.GT5700@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).