All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
Cc: secalert@redhat.com, Jakub Kicinski <kubakici@wp.pl>,
	linux-wireless@vger.kernel.org, kjlu@umn.edu,
	linux-kernel@vger.kernel.org, emamd001@umn.edu,
	linux-mediatek@lists.infradead.org, smccaman@umn.edu,
	Matthias Brugger <matthias.bgg@gmail.com>,
	netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	linux-arm-kernel@lists.infradead.org,
	Navid Emamdoost <navid.emamdoost@gmail.com>
Subject: Re: [PATCH] mt7601u: null check the allocation
Date: Tue,  6 Aug 2019 12:35:48 +0000 (UTC)	[thread overview]
Message-ID: <20190806123549.7C9BD609CD@smtp.codeaurora.org> (raw)
In-Reply-To: <20190724141736.29994-1-navid.emamdoost@gmail.com>

Navid Emamdoost <navid.emamdoost@gmail.com> wrote:

> devm_kzalloc may fail and return NULL. So the null check is needed.
> 
> Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
> Acked-by: Jakub Kicinski <kubakici@wp.pl>

Patch applied to wireless-drivers-next.git, thanks.

b95c732234fa mt7601u: null check the allocation

-- 
https://patchwork.kernel.org/patch/11057013/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Navid Emamdoost <navid.emamdoost@gmail.com>
Cc: secalert@redhat.com, Jakub Kicinski <kubakici@wp.pl>,
	linux-wireless@vger.kernel.org, kjlu@umn.edu,
	linux-kernel@vger.kernel.org, emamd001@umn.edu,
	linux-mediatek@lists.infradead.org, smccaman@umn.edu,
	Matthias Brugger <matthias.bgg@gmail.com>,
	netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	linux-arm-kernel@lists.infradead.org,
	Navid Emamdoost <navid.emamdoost@gmail.com>
Subject: Re: [PATCH] mt7601u: null check the allocation
Date: Tue,  6 Aug 2019 12:35:48 +0000 (UTC)	[thread overview]
Message-ID: <20190806123549.7C9BD609CD@smtp.codeaurora.org> (raw)
In-Reply-To: <20190724141736.29994-1-navid.emamdoost@gmail.com>

Navid Emamdoost <navid.emamdoost@gmail.com> wrote:

> devm_kzalloc may fail and return NULL. So the null check is needed.
> 
> Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
> Acked-by: Jakub Kicinski <kubakici@wp.pl>

Patch applied to wireless-drivers-next.git, thanks.

b95c732234fa mt7601u: null check the allocation

-- 
https://patchwork.kernel.org/patch/11057013/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-08-06 12:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 22:19 [PATCH] mt76_init_sband_2g: null check the allocation Navid Emamdoost
2019-07-23 22:19 ` Navid Emamdoost
2019-07-23 22:19 ` Navid Emamdoost
2019-07-24  5:39 ` Kalle Valo
2019-07-24  5:39   ` Kalle Valo
2019-07-24 14:17   ` [PATCH] mt7601u: " Navid Emamdoost
2019-07-24 14:17     ` Navid Emamdoost
     [not found]     ` <20190724141736.29994-1-navid.emamdoost-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-07-24 17:16       ` Jakub Kicinski
2019-07-24 17:16         ` Jakub Kicinski
2019-07-24 17:16         ` Jakub Kicinski
2019-08-06 12:35     ` Kalle Valo [this message]
2019-08-06 12:35       ` Kalle Valo
2019-08-06 12:35     ` Kalle Valo
2019-08-06 12:35       ` Kalle Valo
     [not found] ` <20190723221954.9233-1-navid.emamdoost-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-07-24 17:15   ` [PATCH] mt76_init_sband_2g: " Jakub Kicinski
2019-07-24 17:15     ` Jakub Kicinski
2019-07-24 17:15     ` Jakub Kicinski

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=20190806123549.7C9BD609CD@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=emamd001@umn.edu \
    --cc=kjlu@umn.edu \
    --cc=kubakici@wp.pl \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=navid.emamdoost@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=secalert@redhat.com \
    --cc=smccaman@umn.edu \
    /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.