From: Steve French <smfrench@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Jeff Layton <jlayton@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [patch 05/10] cifs: convert semaphore to mutex
Date: Sat, 30 Jan 2010 17:49:31 -0600 [thread overview]
Message-ID: <524f69651001301549v2db7e155tfdb3ce18cfae035@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1001301100450.3006@localhost.localdomain>
On Sat, Jan 30, 2010 at 4:03 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Fri, 29 Jan 2010, Steve French wrote:
>> > Looks good, but I'm pretty sure I've seen an equivalent patch on the
>> > linux-cifs-client list before.
>> >
>> >
>> > Reviewed-by: Christoph Hellwig <hch@lst.de>
>>
>> Jeff and I acked the cifs part of the patch series in July - not sure
>> why the series didn't go in.
>>
>> http://marc.info/?l=linux-kernel&m=124859649902788&w=2 looks like the
>> original post
>
> Yeah, the patch was part of a larger series which had problems here
> and there. I forgot to split it out and push it seperately.
>
> Steve, can you pick that up and push it via the cifs tree ? It's
> completely stand alone and does not depend on other patches.
np - will queue for 2.6.34
--
Thanks,
Steve
next prev parent reply other threads:[~2010-01-30 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 4:08 [patch 05/10] cifs: convert semaphore to mutex Steve French
2010-01-30 10:03 ` Thomas Gleixner
2010-01-30 23:49 ` Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-29 20:38 [patch 00/10] semaphore to mutex conversions Thomas Gleixner
2010-01-29 20:38 ` [patch 05/10] cifs: convert semaphore to mutex Thomas Gleixner
2010-01-29 22:29 ` Christoph Hellwig
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=524f69651001301549v2db7e155tfdb3ce18cfae035@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=hch@infradead.org \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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