From: Joe Perches <joe@perches.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, "Gustavo Padovan" <gustavo@padovan.org>,
"Russell King" <rmk+kernel@arm.linux.org.uk>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Terje Bergström" <tbergstrom@nvidia.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Alexandre Courbot" <gnurou@gmail.com>,
"David Airlie" <airlied@linux.ie>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Daniel Vetter" <daniel.vetter@intel.com>,
"Rob Clark" <robdclark@gmail.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] gpu/drm: Use u64_to_user_pointer
Date: Fri, 18 Mar 2016 10:43:31 -0700 [thread overview]
Message-ID: <1458323011.26915.6.camel@perches.com> (raw)
In-Reply-To: <201603190148.px58QxiJ%fengguang.wu@intel.com>
On Sat, 2016-03-19 at 01:39 +0800, kbuild test robot wrote:
> Hi Joe,
>
> [auto build test WARNING on drm/drm-next]
> [also build test WARNING on next-20160318]
> [cannot apply to v4.5]
> [if your patch is applied to the wrong git tree, please drop us a
> note to help improving the system]
Thanks, but this depends on Gustavo's patches too.
next prev parent reply other threads:[~2016-03-18 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 13:27 [PATCH v10 1/3] staging/android: remove redundant comments on sync_merge_data Gustavo Padovan
2016-03-18 13:27 ` [PATCH v10 2/3] kernel.h: add u64_to_user_ptr() Gustavo Padovan
2016-03-18 15:39 ` Joe Perches
2016-03-18 17:20 ` [PATCH] gpu/drm: Use u64_to_user_pointer Joe Perches
2016-03-18 17:39 ` kbuild test robot
2016-03-18 17:43 ` Joe Perches [this message]
2016-03-18 17:43 ` kbuild test robot
2016-03-18 17:46 ` kbuild test robot
2016-03-18 13:27 ` [PATCH v10 3/3] staging/android: refactor SYNC IOCTLs Gustavo Padovan
2016-04-05 18:19 ` Gustavo Padovan
2016-04-14 18:03 ` Gustavo Padovan
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=1458323011.26915.6.camel@perches.com \
--to=joe@perches.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@padovan.org \
--cc=kbuild-all@01.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robdclark@gmail.com \
--cc=swarren@wwwdotorg.org \
--cc=tbergstrom@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox