From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: xgene-dma: Fix "incorrect type in assignement" warnings
Date: Tue, 2 Jun 2015 19:05:38 +0530 [thread overview]
Message-ID: <20150602133538.GZ3140@localhost> (raw)
In-Reply-To: <1433235813-3225-1-git-send-email-rsahu@apm.com>
On Tue, Jun 02, 2015 at 02:33:33PM +0530, Rameshwar Prasad Sahu wrote:
> This patch fixes sparse warnings like incorrect type in assignment
> (different base types), cast to restricted __le64.
>
I am appliying this but ideally you should have split thsi into seprate
patches for each fix
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Rameshwar Prasad Sahu <rsahu-qTEPVZfXA3Y@public.gmane.org>
Cc: dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
jcm-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
patches-qTEPVZfXA3Y@public.gmane.org
Subject: Re: [PATCH] dmaengine: xgene-dma: Fix "incorrect type in assignement" warnings
Date: Tue, 2 Jun 2015 19:05:38 +0530 [thread overview]
Message-ID: <20150602133538.GZ3140@localhost> (raw)
In-Reply-To: <1433235813-3225-1-git-send-email-rsahu-qTEPVZfXA3Y@public.gmane.org>
On Tue, Jun 02, 2015 at 02:33:33PM +0530, Rameshwar Prasad Sahu wrote:
> This patch fixes sparse warnings like incorrect type in assignment
> (different base types), cast to restricted __le64.
>
I am appliying this but ideally you should have split thsi into seprate
patches for each fix
--
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Rameshwar Prasad Sahu <rsahu@apm.com>
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
arnd@arndb.de, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
jcm@redhat.com, patches@apm.com
Subject: Re: [PATCH] dmaengine: xgene-dma: Fix "incorrect type in assignement" warnings
Date: Tue, 2 Jun 2015 19:05:38 +0530 [thread overview]
Message-ID: <20150602133538.GZ3140@localhost> (raw)
In-Reply-To: <1433235813-3225-1-git-send-email-rsahu@apm.com>
On Tue, Jun 02, 2015 at 02:33:33PM +0530, Rameshwar Prasad Sahu wrote:
> This patch fixes sparse warnings like incorrect type in assignment
> (different base types), cast to restricted __le64.
>
I am appliying this but ideally you should have split thsi into seprate
patches for each fix
--
~Vinod
next prev parent reply other threads:[~2015-06-02 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 9:03 [PATCH] dmaengine: xgene-dma: Fix "incorrect type in assignement" warnings Rameshwar Prasad Sahu
2015-06-02 9:03 ` Rameshwar Prasad Sahu
2015-06-02 9:03 ` Rameshwar Prasad Sahu
2015-06-02 13:35 ` Vinod Koul [this message]
2015-06-02 13:35 ` Vinod Koul
2015-06-02 13:35 ` Vinod Koul
2015-06-03 7:07 ` Rameshwar Sahu
2015-06-03 7:07 ` Rameshwar Sahu
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=20150602133538.GZ3140@localhost \
--to=vinod.koul@intel.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 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.