All of lore.kernel.org
 help / color / mirror / Atom feed
From: leonro@mellanox.com (Leon Romanovsky)
To: linux-snps-arc@lists.infradead.org
Subject: arch/arc/ allmodconfig
Date: Sat, 28 Jul 2018 10:59:13 +0300	[thread overview]
Message-ID: <20180728075913.GA7157@mtr-leonro.mtl.com> (raw)
In-Reply-To: <C2D7FE5348E1B147BCA15975FBA23075012B08679D@us01wembx1.internal.synopsys.com>

On Fri, Jul 27, 2018@08:14:31PM +0000, Vineet Gupta wrote:
> On 07/23/2018 10:02 AM, Leon Romanovsky wrote:
> >>> 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 {
> >> Thx for this change. Can you please send a proper patch with changelog, citing the
> >> issue as Reported-by etc.
> >> Also if Mellanox is interested in maintaining the NPS port going fwd, someone (you
> >> ?) should add their name to MAINTAINERS file under arch/arc/plat-eznps and send
> >> that patch as well.
> > Hi Vineet,
> >
> > Thanks for your feedback, I'll work with Ofer to make it happen.
>
> Ping, folks can one of you please send a formal patch for this ?

Vineet,

We sent the fix almost at the same day, but for some reason, the emails
from Ofer didn't arrive to ML.

I resent it,
https://www.mail-archive.com/linux-snps-arc at lists.infradead.org/msg03899.html
https://www.mail-archive.com/linux-snps-arc at lists.infradead.org/msg03864.html

And we will check with IT the reason why Ofer's email didn't work.

Thanks

>
> -Vineet

WARNING: multiple messages have this Message-ID (diff)
From: Leon Romanovsky <leonro@mellanox.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "Ofer Levi(SW)" <oferle@mellanox.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>
Subject: Re: arch/arc/ allmodconfig
Date: Sat, 28 Jul 2018 10:59:13 +0300	[thread overview]
Message-ID: <20180728075913.GA7157@mtr-leonro.mtl.com> (raw)
In-Reply-To: <C2D7FE5348E1B147BCA15975FBA23075012B08679D@us01wembx1.internal.synopsys.com>

On Fri, Jul 27, 2018 at 08:14:31PM +0000, Vineet Gupta wrote:
> On 07/23/2018 10:02 AM, Leon Romanovsky wrote:
> >>> 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 {
> >> Thx for this change. Can you please send a proper patch with changelog, citing the
> >> issue as Reported-by etc.
> >> Also if Mellanox is interested in maintaining the NPS port going fwd, someone (you
> >> ?) should add their name to MAINTAINERS file under arch/arc/plat-eznps and send
> >> that patch as well.
> > Hi Vineet,
> >
> > Thanks for your feedback, I'll work with Ofer to make it happen.
>
> Ping, folks can one of you please send a formal patch for this ?

Vineet,

We sent the fix almost at the same day, but for some reason, the emails
from Ofer didn't arrive to ML.

I resent it,
https://www.mail-archive.com/linux-snps-arc@lists.infradead.org/msg03899.html
https://www.mail-archive.com/linux-snps-arc@lists.infradead.org/msg03864.html

And we will check with IT the reason why Ofer's email didn't work.

Thanks

>
> -Vineet

  reply	other threads:[~2018-07-28  7:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19  5:37 arch/arc/ allmodconfig Randy Dunlap
2018-07-19  5:37 ` Randy Dunlap
2018-07-19 16:21 ` Vineet Gupta
2018-07-19 16:21   ` Vineet Gupta
2018-07-20  7:19   ` Meir Lichtinger
2018-07-20  7:19     ` Meir Lichtinger
2018-07-23  8:34     ` Ofer Levi(SW)
2018-07-23  8:34       ` Ofer Levi(SW)
2018-07-23 16:36       ` Vineet Gupta
2018-07-23 16:36         ` Vineet Gupta
2018-07-23 16:51         ` Leon Romanovsky
2018-07-23 16:51           ` Leon Romanovsky
2018-07-27 20:14           ` Vineet Gupta
2018-07-27 20:14             ` Vineet Gupta
2018-07-28  7:59             ` Leon Romanovsky [this message]
2018-07-28  7:59               ` Leon Romanovsky
2018-07-23 19:45       ` Randy Dunlap
2018-07-23 19:45         ` Randy Dunlap

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=20180728075913.GA7157@mtr-leonro.mtl.com \
    --to=leonro@mellanox.com \
    --cc=linux-snps-arc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.