From: plyatov@gmail.com (Igor Plyatov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] mach-at91: Support for gsia18s board added
Date: Mon, 13 Dec 2010 10:15:40 +0300 [thread overview]
Message-ID: <1292224540.4117.16.camel@homepc> (raw)
In-Reply-To: <20101212140727.GI19897@game.jcrosoft.org>
Dear Jean-Christophe,
> sorry as I explain before if you have exclusive option you need to create
> kconfig options which are board specific to manage them
> we work to reduce the number of defconfig in the mainline
> and it's not PortuxG20 and Stamp9g20 specific but to have only one defconfig
> for all 9g20 at a first step and late for all sam9
Thank you for time spent on my patches and e-mails!
I was think to do it this way, but unsure that this is a right way.
Now, with yours help, I know what to do.
> > > your patch contain a lots of whitespace please fix it
> >
> > There is no problems with whitespace. This patch checked by
> > scripts/checkpatch.pl twice. It seems your mailer corrupt this patch.
> my mailer no way mutt does not do it
> and when I edit with vim I saw the whitespace too
> please check again
I found this whitespaces. There is something strange inside of gedit,
because I does not have practice to use spaces for formatting.
It seems, time to learn vi, come :-)
> > Please, use more testimony why it is required to use system_rev here.
> > Yours position does not clear for me.
> > You can point me to the right documentation or discussion about this
> > requirements in the mail archives...
> two bards with the same machine id NACK as we can not compile them in the same
> kernel and this a target we all work on to allow
> if you want to tuse the same machine id as I did for other boards you must use
> system_rev or any detection to identify tehm
OK. I will use the GSIA18S machine instead of the STAMP9G20.
The GSIA18S already registerd in the ARM machines database.
Best regards!
--
Igor Plyatov
prev parent reply other threads:[~2010-12-13 7:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 17:00 [PATCH v4] mach-at91: Support for gsia18s board added Igor Plyatov
2010-12-12 0:50 ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-12 6:37 ` Igor Plyatov
2010-12-12 14:07 ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-12 14:22 ` Russell King - ARM Linux
2010-12-12 19:52 ` Igor Plyatov
2010-12-12 23:39 ` Russell King - ARM Linux
2010-12-13 6:26 ` Igor Plyatov
2010-12-13 7:15 ` Igor Plyatov [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=1292224540.4117.16.camel@homepc \
--to=plyatov@gmail.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).