From: Greg KH <gregkh@linuxfoundation.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] driver core: Clean up dev_get/set_drvdata
Date: Tue, 27 May 2014 13:50:36 -0700 [thread overview]
Message-ID: <20140527205036.GA4888@kroah.com> (raw)
In-Reply-To: <20140414124802.2859439e@endymion.delvare>
On Mon, Apr 14, 2014 at 12:48:02PM +0200, Jean Delvare wrote:
> This patch set is a proposal to revert most of commit b4028437. This
> would solve a memory leak and also allow to simplify and ultimately
> inline again functions dev_get_drvdata and dev_set_drvdata for smaller
> footprint and improved performance.
>
> [PATCH 1/5] driver core: Move driver_data back to struct device
> [PATCH 2/5] driver core: dev_set_drvdata can no longer fail
> [PATCH 3/5] driver core: dev_set_drvdata returns void
> [PATCH 4/5] driver core: dev_get_drvdata: Don't check for NULL dev
> [PATCH 5/5] driver core: Inline dev_set/get_drvdata
>
Sorry for the long delay, these are finally all now applied to my tree.
greg k-h
next prev parent reply other threads:[~2014-05-27 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 10:48 [PATCH 0/5] driver core: Clean up dev_get/set_drvdata Jean Delvare
2014-04-14 10:54 ` [PATCH 1/5] driver core: Move driver_data back to struct device Jean Delvare
2014-04-14 10:55 ` [PATCH 2/5] driver core: dev_set_drvdata can no longer fail Jean Delvare
2014-04-14 10:56 ` [PATCH 3/5] driver core: dev_set_drvdata returns void Jean Delvare
2014-04-14 10:57 ` [PATCH 4/5] driver core: dev_get_drvdata: Don't check for NULL dev Jean Delvare
2014-04-14 10:58 ` [PATCH 5/5] driver core: Inline dev_set/get_drvdata Jean Delvare
2014-04-14 11:50 ` [PATCH 0/5] driver core: Clean up dev_get/set_drvdata Greg KH
2014-05-27 20:50 ` Greg KH [this message]
2014-05-27 20:57 ` Jean Delvare
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=20140527205036.GA4888@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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.