From: Sergey Matyukevich <geomatsi@gmail.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Ramsay Jones <ramsay@ramsayjones.plus.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-sparse@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: sysreg: fix sparse warnings
Date: Fri, 16 Nov 2018 16:54:24 +0300 [thread overview]
Message-ID: <20181116135424.pbwns66phknezmfa@bars> (raw)
In-Reply-To: <20181116103359.wywpaeanhoceqhgb@ltop.local>
On Fri, Nov 16, 2018 at 11:34:00AM +0100, Luc Van Oostenryck wrote:
> > Hi,
> >
> > Could you please clarify what is your resolution regarding that warning.
> > I pulled all the changes from sparse repository on kernel.org. However
> > the same warning is still here when building modules with C=2 option.
>
> Hi,
>
> Yes, the warning is still there since it's maybe not desired but
> is at least legit. For the short term, I think the best is your
> original patch (but using UL as the prefix). I would be glad to
> ack such a patch (I tried to answer in the original thread but
> I never found it although I should be subscribed to the
> linux-arm-kernel mailing list).
>
> For the slightly longer term, I'll need to see how Ramsay's
> patches can also be used for kernel code.
Thanks for clarifiation! I will send v2.
Regards,
Sergey
WARNING: multiple messages have this Message-ID (diff)
From: geomatsi@gmail.com (Sergey Matyukevich)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: sysreg: fix sparse warnings
Date: Fri, 16 Nov 2018 16:54:24 +0300 [thread overview]
Message-ID: <20181116135424.pbwns66phknezmfa@bars> (raw)
In-Reply-To: <20181116103359.wywpaeanhoceqhgb@ltop.local>
On Fri, Nov 16, 2018 at 11:34:00AM +0100, Luc Van Oostenryck wrote:
> > Hi,
> >
> > Could you please clarify what is your resolution regarding that warning.
> > I pulled all the changes from sparse repository on kernel.org. However
> > the same warning is still here when building modules with C=2 option.
>
> Hi,
>
> Yes, the warning is still there since it's maybe not desired but
> is at least legit. For the short term, I think the best is your
> original patch (but using UL as the prefix). I would be glad to
> ack such a patch (I tried to answer in the original thread but
> I never found it although I should be subscribed to the
> linux-arm-kernel mailing list).
>
> For the slightly longer term, I'll need to see how Ramsay's
> patches can also be used for kernel code.
Thanks for clarifiation! I will send v2.
Regards,
Sergey
next prev parent reply other threads:[~2018-11-16 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 20:47 [PATCH] arm64: sysreg: fix sparse warnings Sergey Matyukevich
2018-11-10 0:16 ` Will Deacon
2018-11-10 11:16 ` Sergey Matyukevich
2018-11-10 17:03 ` Will Deacon
2018-11-10 17:54 ` Luc Van Oostenryck
2018-11-10 17:54 ` Luc Van Oostenryck
2018-11-12 16:32 ` Ramsay Jones
2018-11-12 16:32 ` Ramsay Jones
2018-11-14 22:25 ` Luc Van Oostenryck
2018-11-14 22:25 ` Luc Van Oostenryck
2018-11-15 8:35 ` Sergey Matyukevich
2018-11-15 8:35 ` Sergey Matyukevich
2018-11-16 10:34 ` Luc Van Oostenryck
2018-11-16 10:34 ` Luc Van Oostenryck
2018-11-16 13:54 ` Sergey Matyukevich [this message]
2018-11-16 13:54 ` Sergey Matyukevich
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=20181116135424.pbwns66phknezmfa@bars \
--to=geomatsi@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=marc.zyngier@arm.com \
--cc=ramsay@ramsayjones.plus.com \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@arm.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 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.