All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Thompson <daniel.thompson@linaro.org>
To: Cengiz Can <cengiz@kernel.wtf>
Cc: kgdb-bugreport@lists.sourceforge.net,
	LKML <linux-kernel@vger.kernel.org>,
	Doug Anderson <dianders@chromium.org>
Subject: Re: [PATCH v3] kdb: remove unnecessary null check of dbg_io_ops
Date: Fri, 10 Jul 2020 14:41:46 +0100	[thread overview]
Message-ID: <20200710134146.xk6je7ttp7ksmhj3@holly.lan> (raw)
In-Reply-To: <4b91d92eda95cf4f1e153544ff4c17e1@kernel.wtf>

On Fri, Jul 10, 2020 at 03:15:55PM +0300, Cengiz Can wrote:
> Hello Daniel,
> 
> On 2020-07-01 01:32, Doug Anderson wrote:
> > 
> > Reviewed-by: Douglas Anderson <dianders@chromium.org>
> > Tested-by: Douglas Anderson <dianders@chromium.org>
> 
> Wanted to ask about the status of this proposed patch.
> 
> I have checked your tree in git.kernel.org but you might be
> collecting them somewhere else perhaps.

It's applied... but then holiday happened. Should be pushed out soon.


Daniel.

      reply	other threads:[~2020-07-10 13:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 13:59 [PATCH] kdb: prevent possible null deref in kdb_msg_write Cengiz Can
2020-06-29 14:27 ` Daniel Thompson
2020-06-29 14:50 ` Petr Mladek
2020-06-29 14:53   ` Petr Mladek
2020-06-29 15:37   ` Daniel Thompson
2020-06-29 20:50     ` [PATCH v2] kdb: remove unnecessary null check of dbg_io_ops Cengiz Can
2020-06-29 21:16       ` Doug Anderson
2020-06-29 22:10         ` Cengiz Can
2020-06-30  5:55     ` [PATCH] kdb: prevent possible null deref in kdb_msg_write Sumit Garg
2020-06-30  8:29       ` [PATCH v3] kdb: remove unnecessary null check of dbg_io_ops Cengiz Can
2020-06-30 11:36         ` Sumit Garg
2020-06-30 11:48           ` Andy Shevchenko
2020-06-30 22:32         ` Doug Anderson
2020-07-10 12:15           ` Cengiz Can
2020-07-10 13:41             ` Daniel Thompson [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=20200710134146.xk6je7ttp7ksmhj3@holly.lan \
    --to=daniel.thompson@linaro.org \
    --cc=cengiz@kernel.wtf \
    --cc=dianders@chromium.org \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@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 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.