All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Arend van Spriel" <arend@broadcom.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Linux Wireless List" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 5/5] brcmfmac: introduce checkdied debugfs functionality
Date: Thu, 14 Jun 2012 14:54:32 +0200	[thread overview]
Message-ID: <4FD9DF08.4020304@broadcom.com> (raw)
In-Reply-To: <1339669017-13388-1-git-send-email-arend@broadcom.com>

On 06/14/2012 12:16 PM, Arend van Spriel wrote:
> The checkdied functionality provides useful information for analyzing
> firmware crashes. By exposing this information to a debugfs file users
> can easily provide its content in bug reports. The functionality is
> available only when CONFIG_BRCMDBG is selected.
> 
> Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com>
> Reviewed-by: Franky (Zhenhui) Lin <frankyl@broadcom.com>
> Signed-off-by: Arend van Spriel <arend@broadcom.com>
> ---
> This patch changes kzalloc() to vzalloc(). This replaces patch with
> message-id <1339275105-3593-6-git-send-email-arend@broadcom.com>.
> 
> All 5 patches apply to latest wireless-next/master branch.

Hi John,

Just fetched wireless-next and noticed you already applied the first 4
patches. I tried and this fifth patch does apply to wireless-next/master.

Gr. AvS


      reply	other threads:[~2012-06-14 12:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 10:16 [PATCH v2 5/5] brcmfmac: introduce checkdied debugfs functionality Arend van Spriel
2012-06-14 12:54 ` Arend van Spriel [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=4FD9DF08.4020304@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 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.