From: Greg KH <gregkh@linuxfoundation.org>
To: Wang YanQing <udknight@gmail.com>,
jslaby@suse.cz, alan@linux.intel.com, airlied@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] Convert all to the caller hold lock version
Date: Mon, 20 May 2013 12:27:37 -0700 [thread overview]
Message-ID: <20130520192737.GA20961@kroah.com> (raw)
In-Reply-To: <20130508181304.GA12344@udknight>
On Thu, May 09, 2013 at 02:13:04AM +0800, Wang YanQing wrote:
> After commit 50e244cc793d511b86adea24972f3a7264cae114
> (fb: rework locking to fix lock ordering on takeover)
> and
> commit e93a9a868792ad71cdd09d75e5a02d8067473c4e
> (fb: Yet another band-aid for fixing lockdep mess)
>
> We have two version functions implement almost the same function,
> except the caller/callee hold lock.
>
> fbcon_takeover vs do_fbcon_takeover
> register_con_driver vs do_register_con_driver
> take_over_console vs do_take_over_console
> unbind_con_driver vs do_unbind_con_driver
> bind_con_driver vs do_bind_con_driver
> unregister_con_driver vs do_unregister_con_driver
>
> This issue bring us much code duplication,
> like do_fbcon_takeover and fbcon_takeover,
> they have almost the same.
>
> Although some of them had been re-written
> as a wrapper for another, but the wrapper
> is so trivial, we can just throw them away.
>
> Also those two versions of almost the same
> functions will confuse API's user.
>
> After all, I think this issue is not good
> for long time maintain.
>
> This series patch convert all to the
> new version which caller hold the lock,
> and then delete the old version away.
Can you also send a patch fixing up the documentation to use the new
functions as well?
thanks,
greg k-h
next prev parent reply other threads:[~2013-05-20 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 18:13 [PATCH 0/9] Convert all to the caller hold lock version Wang YanQing
2013-05-20 19:27 ` Greg KH [this message]
2013-05-21 0:48 ` Wang YanQing
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=20130520192737.GA20961@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@redhat.com \
--cc=alan@linux.intel.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=udknight@gmail.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