From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] staging/vchi: Fix some pointer math for 64-bit.
Date: Tue, 25 Oct 2016 09:55:15 +0200 [thread overview]
Message-ID: <20161025075515.GA29765@kroah.com> (raw)
In-Reply-To: <20161017194406.1080-4-eric@anholt.net>
On Mon, Oct 17, 2016 at 12:44:04PM -0700, Eric Anholt wrote:
> These were throwing warnings on aarch64, and all are trivially
> converted to longs.
>
> Signed-off-by: Eric Anholt <eric@anholt.net>
> ---
> drivers/staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.c | 6 +++---
> drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c | 5 +++--
> 2 files changed, 6 insertions(+), 5 deletions(-)
This didnt apply anymore as I think I took the other fixups, sorry.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eric Anholt <eric@anholt.net>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
Dom Cobley <popcornmix@gmail.com>
Subject: Re: [PATCH 3/5] staging/vchi: Fix some pointer math for 64-bit.
Date: Tue, 25 Oct 2016 09:55:15 +0200 [thread overview]
Message-ID: <20161025075515.GA29765@kroah.com> (raw)
In-Reply-To: <20161017194406.1080-4-eric@anholt.net>
On Mon, Oct 17, 2016 at 12:44:04PM -0700, Eric Anholt wrote:
> These were throwing warnings on aarch64, and all are trivially
> converted to longs.
>
> Signed-off-by: Eric Anholt <eric@anholt.net>
> ---
> drivers/staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.c | 6 +++---
> drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c | 5 +++--
> 2 files changed, 6 insertions(+), 5 deletions(-)
This didnt apply anymore as I think I took the other fixups, sorry.
greg k-h
next prev parent reply other threads:[~2016-10-25 7:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 19:44 [PATCH 0/5] staging/vchi: Start on 64-bit cleanup, TODO file Eric Anholt
2016-10-17 19:44 ` Eric Anholt
2016-10-17 19:44 ` [PATCH 1/5] staging/vchi: Fix build error in debugfs ops on aarch64 Eric Anholt
2016-10-17 19:44 ` Eric Anholt
2016-10-17 20:28 ` Greg Kroah-Hartman
2016-10-17 20:28 ` Greg Kroah-Hartman
2016-10-17 19:44 ` [PATCH 2/5] staging/vchi: Fix build warnings when formatting pointers " Eric Anholt
2016-10-17 19:44 ` Eric Anholt
2016-10-17 20:28 ` Greg Kroah-Hartman
2016-10-17 20:28 ` Greg Kroah-Hartman
2016-10-17 23:38 ` Eric Anholt
2016-10-17 23:38 ` Eric Anholt
2016-10-18 6:41 ` Greg Kroah-Hartman
2016-10-18 6:41 ` Greg Kroah-Hartman
2016-10-17 19:44 ` [PATCH 3/5] staging/vchi: Fix some pointer math for 64-bit Eric Anholt
2016-10-17 19:44 ` Eric Anholt
2016-10-25 7:55 ` Greg Kroah-Hartman [this message]
2016-10-25 7:55 ` Greg Kroah-Hartman
2016-10-25 15:44 ` Eric Anholt
2016-10-25 15:44 ` Eric Anholt
2016-10-17 19:44 ` [PATCH 4/5] staging/vchi: Add a TODO file of things I know we need to deal with Eric Anholt
2016-10-17 19:44 ` Eric Anholt
2016-10-18 14:54 ` popcorn mix
2016-10-18 14:54 ` popcorn mix
2016-10-17 19:44 ` [PATCH 5/5] MAINTAINERS: Add the staging vchiq driver as a bcm2835 responsibility Eric Anholt
2016-10-17 19:44 ` Eric Anholt
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=20161025075515.GA29765@kroah.com \
--to=gregkh@linuxfoundation.org \
--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.