public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora•org>
To: Nicholas Krause <xerofoify@gmail•com>
Cc: stefano.brivio@polimi•it, linux-wireless@vger•kernel.org,
	b43-dev@lists•infradead.org, netdev@vger•kernel.org,
	linux-kernel@vger•kernel.org
Subject: Re: [PATCH] drivers:net:wireless: Add proper locking for the function, b43_op_beacon_set_tim in main.c
Date: Mon, 05 Jan 2015 11:29:50 +0200	[thread overview]
Message-ID: <87tx05378x.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1420184041-6788-1-git-send-email-xerofoify@gmail.com> (Nicholas Krause's message of "Fri, 2 Jan 2015 02:34:01 -0500")

Nicholas Krause <xerofoify@gmail•com> writes:

> This adds proper locking for the function, b43_op_beacon_set_tim in
> main.c by using the mutex lock in the structure pointer wl, as
> embedded into this pointer as a mutex in order to protect against
> multiple access to the pointer wl when updating the templates for this
> pointer in the function, b43_update_templates internally in the
> function, b43_op_beacon_set_tim.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail•com>

Based on the discussion I have dropped this patch.

-- 
Kalle Valo

  parent reply	other threads:[~2015-01-05  9:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02  7:34 [PATCH] drivers:net:wireless: Add proper locking for the function, b43_op_beacon_set_tim in main.c Nicholas Krause
2015-01-02  9:27 ` Michael Büsch
2015-01-02 11:19   ` Rafał Miłecki
2015-01-02 11:42     ` Michael Büsch
2015-01-02 17:13   ` nick
2015-01-02 16:40 ` Larry Finger
2015-01-05  9:29 ` Kalle Valo [this message]
     [not found]   ` <87tx05378x.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2015-01-05 17:16     ` nick
2015-01-05 17:46       ` Larry Finger
     [not found]         ` <54AACE00.8060407-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2015-01-05 18:21           ` nick

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=87tx05378x.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora$(echo .)org \
    --cc=b43-dev@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-wireless@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=stefano.brivio@polimi$(echo .)it \
    --cc=xerofoify@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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