From: Greg KH <greg@kroah.com>
To: Mark Peloquin <peloquin@us.ibm.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
evms-devel@lists.sourceforge.net
Subject: Re: [PATCH] add safe version of list_for_each_entry() to list.h
Date: Thu, 3 Oct 2002 16:44:30 -0700 [thread overview]
Message-ID: <20021003234430.GG2289@kroah.com> (raw)
In-Reply-To: <OF9EDF8472.CDE2D9D8-ON85256C47.0080772B@pok.ibm.com>
On Thu, Oct 03, 2002 at 06:42:09PM -0500, Mark Peloquin wrote:
> Please consider adding the following patch to list.h.
This patch had the tabs mangled and would not apply.
Yeah, Notes sucks for sending patches...
thanks,
greg k-h
next prev parent reply other threads:[~2002-10-03 23:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 23:42 [PATCH] add safe version of list_for_each_entry() to list.h Mark Peloquin
2002-10-03 23:44 ` Greg KH [this message]
2002-10-04 0:25 ` Kevin Corry
2002-10-04 13:58 ` Christoph Hellwig
2002-10-04 13:48 ` Kevin Corry
2002-10-04 13:51 ` Kevin Corry
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 15:05 Matthew Wilcox
2002-10-04 15:48 Mark Peloquin
2002-10-04 16:00 ` Matthew Wilcox
2002-10-04 16:33 ` Andrew Morton
2002-10-04 16:40 Mark Peloquin
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=20021003234430.GG2289@kroah.com \
--to=greg@kroah.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peloquin@us.ibm.com \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox