public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Andreea Bernat <bernat.ada@gmail.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: Elena Oat <oat.elena@gmail.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Paul McKenney <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH] rtl8188eu: Replace rcu_dereference() with rcu_access_pointer()
Date: Thu, 04 Sep 2014 16:23:23 -0500	[thread overview]
Message-ID: <5408D84B.7040302@lwfinger.net> (raw)
In-Reply-To: <CALDM6bpomcGJk1Ut2hb8qO0gYeKkHruJZ0duBwAaonFf6HbZwA@mail.gmail.com>

On 09/04/2014 03:58 PM, Andreea Bernat wrote:
> Hello,
>
> I cloned this:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
>
> and after moved to staging-next branch, but in both cases, in
> those files I don't find any use of rcu_dereference() call (the call
> which I am looking for to modify).

The rcu_dereference() call in core/rtw_mlme.c is no longer there in mainline 
3.17, thus it was removed some time ago.

There is a similar reference in os_dep/recv_linux.c. Perhaps it should be removed.

This problem shows the importance of working with the latest pull of the staging 
repo when working with staging code. Even then patches may suffer mid-air 
collisions if multiple devs are working on a particular piece of code.

Larry



  reply	other threads:[~2014-09-04 21:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-17 11:43 [PATCH] rtl8188eu: Replace rcu_dereference() with rcu_access_pointer() Andreea-Cristina Bernat
2014-08-30 20:42 ` Greg KH
2014-09-04 20:58   ` Andreea Bernat
2014-09-04 21:23     ` Larry Finger [this message]
2014-09-04 21:38     ` Greg KH
2014-09-05 18:21       ` Andreea Bernat

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=5408D84B.7040302@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bernat.ada@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oat.elena@gmail.com \
    --cc=paulmck@linux.vnet.ibm.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