From: Louis Zhuang <louis.zhuang@linux.co.intel.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
FITHML <fault-injection-developer@lists.sourceforge.net>
Subject: [TRIVIAL PATCH] fix and export kset_find_obj
Date: 14 Jan 2003 11:42:05 +0800 [thread overview]
Message-ID: <1042515724.3951.5.camel@hawk.sh.intel.com> (raw)
Dear Mochel,
I suggest to export kset_find_obj. Pls apply. ;-)
--
Yours truly,
Louis Zhuang
---------------
Fault Injection Test Harness Project
BK tree: http://fault-injection.bkbits.net/linux-2.5
Home Page: http://sf.net/projects/fault-injection
You can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or apply the patch as usual.
===================================================================
ChangeSet@1.970, 2003-01-14 11:34:48+08:00, louis@hawk.sh.intel.com
trivial fix and export kset_find_obj
include/linux/kobject.h | 2 +-
lib/kobject.c | 4 +++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff -Nru a/include/linux/kobject.h b/include/linux/kobject.h
--- a/include/linux/kobject.h Tue Jan 14 11:36:05 2003
+++ b/include/linux/kobject.h Tue Jan 14 11:36:05 2003
@@ -87,7 +87,7 @@
}
-extern struct kobject * kset_find_obj(struct kset *, char *);
+extern struct kobject * kset_find_obj(struct kset *, const char *);
struct subsystem {
diff -Nru a/lib/kobject.c b/lib/kobject.c
--- a/lib/kobject.c Tue Jan 14 11:36:05 2003
+++ b/lib/kobject.c Tue Jan 14 11:36:05 2003
@@ -295,7 +295,7 @@
* looking for a matching kobject. Return object if found.
*/
-struct kobject * kset_find_obj(struct kset * kset, char * name)
+struct kobject * kset_find_obj(struct kset * kset, const char * name)
{
struct list_head * entry;
struct kobject * ret = NULL;
@@ -386,6 +386,8 @@
EXPORT_SYMBOL(kobject_unregister);
EXPORT_SYMBOL(kobject_get);
EXPORT_SYMBOL(kobject_put);
+
+EXPORT_SYMBOL(kset_find_obj);
EXPORT_SYMBOL(subsystem_init);
EXPORT_SYMBOL(subsystem_register);
===================================================================
This BitKeeper patch contains the following changesets:
1.970
## Wrapped with gzip_uu ##
begin 664 bkpatch3959
M'XL(`*6%(SX``\55:VO;,!3]'/V*"_W2Q^)<O6S'(Z/K@ZVLHR%=88-!46VY
M]N)8Q5;2#/SC)[MK2]9FI:50VTB@*QT=G7.$-^"LUE74*\P\K\D&?#:UC7J9
MNIYZ=>;EI=6%%YN9JTR,<95!9F9ZT,T>,$_VTYRXVEC9.(.%KNJH1SU^-V)_
M7^FH-SG\=';\<4+(:`3[F2HO]:FV,!H1:ZJ%*I)Z5]FL,*5G*U76,VU5NV5S
M-[5AB,R]D@8<I=]0'T70Q#2A5`FJ$V0B]`7I2.T^H+Z*PY%2X5K&_(8)I)P<
M`/6&`0+R`=(!%4!IQ$4DPAT,(T18`PL[#/I(]N!U#[%/8K!5OLA5`6F^!%4F
MH)=7IK(PK;4]3_,R.3<7O\@78%(*2<;WDI+^,Q]"4"'Y`#,39[K8-752>*:Z
M;(K\8C!UF^C8>G%'G#K)G')#%`W*H>0-9VE*&2J%88B)3-?)]!#KKP-<"-9@
MZ/OL$0)Y&1?SQ.4L+^?+N^79*I6@010A-MSW*4L%7H2!#(20:ZG\!_6>%&VD
M#,.@"^N:!6UT7Y7Q<]!:IIPZCD(XIAQ%%V`:/,@O?2J_%/KT+?-[H_,)]*OK
M[G-Y'*^3_`71/A@B4'+4M7II=55";:MY[(C<H,+V*J7-V[(;A.UW$)NRMA!G
MJH+MK?==(%;"_%@,7G!SGL9H+4<JF=\&2$I*UUG.GK*<O['EW77_Q_&5X[[$
M9S8,6Z-ONN=8W'6K/D.I9GJ+'/$P!$9^DL/OXY/)M_/3'U_W3HXW5[#:2-S^
7YYR!\;2>ST9*.[.%4N0/H;:>H5@'````
`
end
next reply other threads:[~2003-01-14 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 3:42 Louis Zhuang [this message]
2003-01-14 15:39 ` [TRIVIAL PATCH] fix and export kset_find_obj Patrick Mochel
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=1042515724.3951.5.camel@hawk.sh.intel.com \
--to=louis.zhuang@linux.co.intel.com \
--cc=fault-injection-developer@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox