dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [GIT PULL] drm/tegra: Fixes for v5.1-rc2
Date: Fri, 22 Mar 2019 14:15:17 +0100	[thread overview]
Message-ID: <20190322131517.825-1-thierry.reding@gmail.com> (raw)

Hi Dave,

The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:

  Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)

are available in the Git repository at:

  git://anongit.freedesktop.org/tegra/linux tags/drm/tegra/for-5.1-rc2

for you to fetch changes up to 509869a2fec36ecb2b841180915995f41d5a0219:

  drm/tegra: vic: Fix implicit function declaration warning (2019-03-22 14:08:55 +0100)

I'm a little late sending this out, so I realize this will probably go
into v5.1-rc3 despite the name of the tag.

Thanks,
Thierry

----------------------------------------------------------------
drm/tegra: Fixes for v5.1-rc2

These are a couple of minor fixes for build issues and sparse warnings.

----------------------------------------------------------------
Anders Roxell (1):
      drm/tegra: vic: Fix implicit function declaration warning

Thierry Reding (1):
      drm/tegra: hub: Fix dereference before check

 drivers/gpu/drm/tegra/hub.c | 4 +++-
 drivers/gpu/drm/tegra/vic.c | 2 ++
 2 files changed, 5 insertions(+), 1 deletion(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-03-22 13:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 13:15 Thierry Reding [this message]
2019-04-03 16:06 ` [GIT PULL] drm/tegra: Fixes for v5.1-rc2 Thierry Reding
2019-04-04  2:15   ` Dave Airlie
2019-04-04 11:33     ` Thierry Reding
2019-04-05 19:45       ` Sean Paul
2019-04-08  9:05         ` Maxime Ripard

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=20190322131517.825-1-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-tegra@vger.kernel.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