linux-kernel - Re: [PATCH v4] mach-at91: Support for gsia18s board added

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 13 Dec 2010 10:15:40 +0300
From:	Igor Plyatov <plyatov@...il.com>
To:	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux@...im.org.za, nicolas.ferre@...el.com,
	linux@....linux.org.uk, costa.antonior@...il.com,
	ryan@...ewatersys.com, christian.glindkamp@...kit.de,
	pgsellmann@...tner-elektronik.at
Subject: Re: [PATCH v4] mach-at91: Support for gsia18s board added

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/