From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Arnd Bergmann <arnd@arndb.de>,
"sachin.kamat@linaro.org" <sachin.kamat@linaro.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
James Hogan <james.hogan@imgtec.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Will Deacon <will.deacon@arm.com>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Richard Kuo <rkuo@codeaurora.org>
Subject: Re: [PATCH] arc: kernel: add default extern variable 'screen_info' in "setup.c"
Date: Thu, 28 Nov 2013 17:07:05 +0800 [thread overview]
Message-ID: <529707B9.1090809@gmail.com> (raw)
Hello Vineet:
hexagon meets the same issue, could you help send related patch for it?
If you have no time, please let me know, I should send it within next
month.
BTW: I assume hexagon need not support VGA_CONSOLE, either, if it is
incorrect, please let me know thanks.
> On 10/24/2013 07:50 PM, Vineet Gupta wrote:
>> On 10/24/2013 04:56 PM, Chen Gang wrote:
>>> If what you said is correct, could you help to send related patch for
>>> it? if I send this kind of patches, it will be easily redirected to
>>> "/dev/null".
>>
>> Geert has explained the state of things quite nicely. Please send your patch to
>> introduce HAVE_xxx. I'm sure maintainers will respond to it as it is the correct
>> thing to do. But I don't want to add bloat to kernel for a random defconfig
>> failure which no one will really use for ARC.
>>
>> If you think u can't/won't do it - let me know and I'll send the patches instead.
>>
>
> Please help send.
>
> Thanks. :-)
>
--
Chen Gang
next reply other threads:[~2013-11-28 9:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 9:07 Chen Gang [this message]
2013-12-06 0:58 ` [PATCH] arc: kernel: add default extern variable 'screen_info' in "setup.c" rkuo
2013-12-06 2:03 ` Chen Gang
2013-12-24 3:18 ` Chen Gang
-- strict thread matches above, loose matches on Subject: below --
2013-10-23 11:09 Chen Gang
2013-10-23 13:47 ` Vineet Gupta
2013-10-24 2:56 ` Chen Gang
2013-10-24 8:30 ` Geert Uytterhoeven
2013-10-24 11:23 ` Chen Gang
2013-10-24 11:50 ` Vineet Gupta
2013-10-26 2:11 ` Chen Gang
2013-10-24 11:51 ` Geert Uytterhoeven
2013-10-26 2:13 ` Chen Gang
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=529707B9.1090809@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=Catalin.Marinas@arm.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rkuo@codeaurora.org \
--cc=sachin.kamat@linaro.org \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).