From: Randy Dunlap <rdunlap@infradead.org>
To: "Ofer Levi(SW)" <oferle@mellanox.com>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Cc: Leon Romanovsky <leonro@mellanox.com>,
Meir Lichtinger <meirl@mellanox.com>
Subject: Re: arch/arc/ allmodconfig
Date: Mon, 23 Jul 2018 12:45:26 -0700 [thread overview]
Message-ID: <82c3e518-a579-7df9-4c3f-8ecb5615b6d7@infradead.org> (raw)
In-Reply-To: <DB6PR05MB4597A63819F227B17652B5B2B2560@DB6PR05MB4597.eurprd05.prod.outlook.com>
On 07/23/2018 01:34 AM, Ofer Levi(SW) wrote:
> Hi Vineet, randy
>
> Indeed this structure is missing, following is a patch based on linux-4.17.9.
> Sorry about that.
>
> Thanks
>
>
> diff -uprN linux-4.17.9.org/arch/arc/plat-eznps/include/plat/ctop.h linux-4.17.9/arch/arc/plat-eznps/include/plat/ctop.h
> --- linux-4.17.9.org/arch/arc/plat-eznps/include/plat/ctop.h 2018-07-22 16:16:09.000000000 +0300
> +++ linux-4.17.9/arch/arc/plat-eznps/include/plat/ctop.h 2018-07-23 11:18:12.179402620 +0300
> @@ -143,6 +143,15 @@ struct nps_host_reg_gim_p_int_dst {
> };
>
> /* AUX registers definition */
> +struct nps_host_reg_aux_dpc {
> + union {
> + struct {
> + u32 ien:1, men:1, hen:1, reserved:29;
> + };
> + u32 value;
> + };
> +};
> +
> struct nps_host_reg_aux_udmc {
> union {
> struct {
>
Thanks, this fixes the build error.
I will not that outlook is not the best email client that you could use for
sending Linux patches. I don't know if you generated the patch with spaces
or tabs being used for indentation, but above, it contains all leading spaces
for indentation, which is Not Good.
--
~Randy
prev parent reply other threads:[~2018-07-23 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 5:37 arch/arc/ allmodconfig Randy Dunlap
2018-07-19 16:21 ` Vineet Gupta
2018-07-20 7:19 ` Meir Lichtinger
2018-07-23 8:34 ` Ofer Levi(SW)
2018-07-23 16:36 ` Vineet Gupta
2018-07-23 16:51 ` Leon Romanovsky
2018-07-27 20:14 ` Vineet Gupta
2018-07-28 7:59 ` Leon Romanovsky
2018-07-23 19:45 ` Randy Dunlap [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=82c3e518-a579-7df9-4c3f-8ecb5615b6d7@infradead.org \
--to=rdunlap@infradead.org \
--cc=Vineet.Gupta1@synopsys.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=meirl@mellanox.com \
--cc=oferle@mellanox.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).