From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Jesper Nilsson <jesper.nilsson@axis.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michal Simek <monstr@monstr.eu>,
Rob Herring <rob.herring@calxeda.com>,
Paul Bolle <pebolle@tiscali.nl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mikael Starvik <starvik@axis.com>,
Jesper Nilsson <jespern@axis.com>, Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] arch/microblaze/kernel/setup.c: Add default 'screen_info" for fixing compiling break
Date: Sat, 20 Sep 2014 12:08:30 +0800 [thread overview]
Message-ID: <541CFDBE.6090600@gmail.com> (raw)
In-Reply-To: <5416C941.9020503@gmail.com>
On 09/15/2014 07:10 PM, Chen Gang wrote:
> On 9/15/14 16:50, Jesper Nilsson wrote:
>> On Sun, Sep 14, 2014 at 10:45:23AM +0200, Geert Uytterhoeven wrote:
[...]
>>
>> Sounds reasonable, at least it can avoid the specific depends on !*arch* cruft.
>>
>
> Thank you very much, next when I try the ARCH_MIGHT_HAVE_VGA, I shall
> process it (remove useless "screen_info").
>
Excuse me, after some trying, I guess, at present, I am not suitable to
perform global architecture wide patches (e.g. ARCH_MIGHT_HAVE_VGA). So
welcome any other members to help try.
I guess, in the future, after I finish all architectures allmodconfig,
I shall be suitable for sending global architecture wide patches.
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
prev parent reply other threads:[~2014-09-20 4:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 8:32 [PATCH] arch/microblaze/kernel/setup.c: Add default 'screen_info" for fixing compiling break Chen Gang
2014-09-14 8:45 ` Geert Uytterhoeven
2014-09-14 9:02 ` Chen Gang
2014-09-16 9:23 ` Michal Simek
2014-09-16 10:04 ` Geert Uytterhoeven
2014-09-16 10:59 ` Michal Simek
2014-09-16 14:34 ` Chen Gang
2014-09-15 8:50 ` Jesper Nilsson
2014-09-15 11:10 ` Chen Gang
2014-09-20 4:08 ` Chen Gang [this message]
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=541CFDBE.6090600@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=jesper.nilsson@axis.com \
--cc=jespern@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=pebolle@tiscali.nl \
--cc=rob.herring@calxeda.com \
--cc=starvik@axis.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).