mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Philip Cox" <Philip.Cox@amd.com>,
	"Oded Gabbay" <oded.gabbay@gmail.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"David (ChunMing) Zhou" <David1.Zhou@amd.com>,
	"David Airlie" <airlied@linux.ie>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Kees Cook" <keescook@chromium.org>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/amdkfd: Fix missing break in switch statement
Date: Mon, 22 Jul 2019 14:47:21 -0500	[thread overview]
Message-ID: <f9b47ccc-d8e8-e03b-dc0c-6c8f1fd36477@embeddedor.com> (raw)
In-Reply-To: <CADnq5_NRDy1jpa2MGefo7KbUB2vejuLwpnJh=vsqyp56yY31Sg@mail.gmail.com>



On 7/22/19 2:45 PM, Alex Deucher wrote:

>>
>> By the way, Alex, I'm planning to add these fixes to my tree. I want
>> to send a pull-request to Linus for v5.3-rc2 this afternoon. We want
>> to have the -Wimplicit-fallthrough option globally enabled in v5.3,
>> and these are some of the last fall-through warnings remaining in
>> the kernel.
>>
>> Can I have your Ack or Signed-off-by for all these drm patches?
> 
> I didn't realize you were sending these yourself. I was going to
> include them in my upcoming -fixes pull.  Feel free to add my RB to
> all three.
> 

Awesome! :)

Thanks
--
Gustavo

      reply	other threads:[~2019-07-22 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-21 21:49 Gustavo A. R. Silva
2019-07-22 19:10 ` Alex Deucher
2019-07-22 19:19   ` Gustavo A. R. Silva
2019-07-22 19:45     ` Alex Deucher
2019-07-22 19:47       ` Gustavo A. R. Silva [this message]

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=f9b47ccc-d8e8-e03b-dc0c-6c8f1fd36477@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=David1.Zhou@amd.com \
    --cc=Philip.Cox@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oded.gabbay@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome