From: Tejun Heo <htejun@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Alan Stern <stern@rowland.harvard.edu>,
Andrew Morton <akpm@linux-foundation.org>,
oliver@neukum.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
zaitcev@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 1/2 UPDATED] klist: implement KLIST_INIT() and DEFINE_KLIST()
Date: Sat, 26 Apr 2008 07:40:04 +0900 [thread overview]
Message-ID: <48125DC4.4000705@gmail.com> (raw)
In-Reply-To: <20080425223027.GA12643@kroah.com>
Greg KH wrote:
> On Sat, Apr 26, 2008 at 03:16:04AM +0900, Tejun Heo wrote:
>> klist is missing static initializers and definition helper. Add them.
>>
>> Signed-off-by: Tejun Heo <htejun@gmail.com>
>> Cc: Peter Zijlstra <peterz@infradead.org>
>> ---
>> Updated to use _name.k_lock as advised.
>
> Thanks, was there a 2/2 patch in this series as well that I should be
> applying?
Yeap, it's named "[PATCH] klist: implement klist_add_{after|before}()".
I forgot to add "2/2".
Thanks.
--
tejun
next prev parent reply other threads:[~2008-04-25 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 9:57 [PATCH 1/2] klist: implement KLIST_INIT() and DEFINE_KLIST() Tejun Heo
2008-04-22 9:58 ` [PATCH] klist: implement klist_add_{after|before}() Tejun Heo
2008-04-28 23:51 ` patch klist-implement-klist_add_-after-before.patch added to gregkh-2.6 tree gregkh
2008-04-22 12:57 ` [PATCH 1/2] klist: implement KLIST_INIT() and DEFINE_KLIST() Peter Zijlstra
2008-04-22 13:03 ` Tejun Heo
2008-04-22 13:06 ` Peter Zijlstra
2008-04-22 13:10 ` Tejun Heo
2008-04-25 16:37 ` Greg KH
2008-04-25 18:16 ` [PATCH 1/2 UPDATED] " Tejun Heo
2008-04-25 22:30 ` Greg KH
2008-04-25 22:40 ` Tejun Heo [this message]
2008-04-28 23:51 ` patch klist-implement-klist_init-and-define_klist.patch added to gregkh-2.6 tree gregkh
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=48125DC4.4000705@gmail.com \
--to=htejun@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=zaitcev@redhat.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 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.