From: Christoph Hellwig <hch@lst.de>
To: linux-kernel@vger.kernel.org
Subject: [hch: Re: [PATCH] cifs: handle termination of cifs oplockd kernel thread]
Date: Fri, 29 Apr 2005 16:35:45 +0200 [thread overview]
Message-ID: <20050429143545.GB7592@lst.de> (raw)
sorry, forgot to Cc lkml
----- Forwarded message from Christoph Hellwig <hch> -----
Date: Fri, 29 Apr 2005 16:34:51 +0200
From: Christoph Hellwig <hch>
Subject: Re: [PATCH] cifs: handle termination of cifs oplockd kernel thread
To: sfrench@us.ibm.com
care to explain what
http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=f28ac91b0541a49d5bc7bfb9f0efd5289a7dd181
does and who revied that? Things like that don't have a business in the
kernel, and certainly not as ioctl.
----- End forwarded message -----
reply other threads:[~2005-04-29 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050429143545.GB7592@lst.de \
--to=hch@lst.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®