From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Li Chaoming <chaoming_li@realsil.com.cn>
Subject: Re: [PATCH 4/6] rtlwifi: Add changes for new vendor driver version
Date: Fri, 24 Aug 2012 10:59:22 +0200 [thread overview]
Message-ID: <20120824085921.GB2982@redhat.com> (raw)
In-Reply-To: <503660D3.5040703@lwfinger.net>
Hi Larry
On Thu, Aug 23, 2012 at 11:56:51AM -0500, Larry Finger wrote:
> >Could Realsil/Realtek post small patches please?
> >
> >See "Separate your changes." from Documentation/SubmittingPatches.
> >
> >You must have separate patches in repositories already. Life is strange,
> >but I don't believe Realsil/Realtek develops driver without source
> >control :-)
>
> Sorry for making the patch so large.
>
> I have no idea what Realtek uses for version control, but I have no
> access to it. What I get from them is a complete new version of a
> driver. To discover what changes have been made, I diff the new
> version against the old and prepare the necessary patches for the
> in-kernel versions, which have diverged from the vendor version.
> Most of the changes are cosmetic, but not all of them fit that
> category. When patches are submitted, I mark them as from Realtek
> authors when that is appropriate. If the change is something that I
> instituted, then I claim authorship. In either case, I am the one
> that prepared the patch.
Ok, I thought/hoped that Realtek is involved into that patch submission.
But if that is only your work, based on vendor driver release, I don't
want you to separate patches into smaller paces, since that is very
tedious work.
> >How this is suppose to work, this variable will be overwritten by
> >any ->pci_probe ? In general this buddy/glabal_var stuff is very
> >fishy, but I did not looked in detail at that. Does all of
> >that actually work ?
>
> The question of whether it works will need to be deferred to
> Chaoming. The situation is that the device has both a 2.4 GHz part
> and a 5 GHz part that register as two separate devices; however,
> each driver instance needs to have access to some of the private
> variables of the other. Can you point me to an example of a safe way
> to do this without using a global variable?
Global variable is fine for that, but this need to be done carefully.
Thanks
Stanislaw
next prev parent reply other threads:[~2012-08-24 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 15:00 [PATCH 0/6] Updates to rtlwifi family to match latest vendor version Larry Finger
2012-08-21 15:00 ` [PATCH 1/6] rtlwifi: rtl8192c: rtl8192de: Fix typo in cursta_connectctate Larry Finger
2012-08-21 15:00 ` [PATCH 2/6] rtlwifi: rtl8192c: rtl8192ce: rtl8192cu: rtl8192se: Remove sparse warnings Larry Finger
2012-08-21 15:00 ` [PATCH 3/6] rtlwifi: Update header file Larry Finger
2012-08-21 15:00 ` [PATCH 4/6] rtlwifi: Add changes for new vendor driver version Larry Finger
2012-08-22 10:50 ` Stanislaw Gruszka
2012-08-23 16:56 ` Larry Finger
2012-08-24 8:59 ` Stanislaw Gruszka [this message]
2012-08-21 15:00 ` [PATCH 5/6] rtlwifi: rtl8192ce: Update " Larry Finger
2012-08-21 15:00 ` [PATCH 6/6] rtlwifi: rtl8192se: Update driver for changes in 12/30/2011 vendor version Larry Finger
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=20120824085921.GB2982@redhat.com \
--to=sgruszka@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).