From: "David S. Miller" <davem@redhat.com>
To: jt@hpl.hp.com
Cc: jt@bougret.hpl.hp.com, shemminger@osdl.org,
irda-users@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [PATCH] convert ircomm to seq_file interface
Date: Tue, 19 Aug 2003 21:20:09 -0700 [thread overview]
Message-ID: <20030819212009.36a8dc03.davem@redhat.com> (raw)
In-Reply-To: <20030818200923.GC6577@bougret.hpl.hp.com>
On Mon, 18 Aug 2003 13:09:23 -0700
Jean Tourrilhes <jt@bougret.hpl.hp.com> wrote:
> On Mon, Aug 18, 2003 at 12:31:42PM -0700, Stephen Hemminger wrote:
> > Convert ircomm /proc interface to seq_file.
> >
> > Note: don't need spin_lock_irq because list is not ever locked
> > from inside interrupt context.
>
> I don't agree with this change.
I'll let you guys work this one out. Let me know when a
final version of the patch is ready.
next prev parent reply other threads:[~2003-08-20 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 19:31 [PATCH] convert ircomm to seq_file interface Stephen Hemminger
2003-08-18 20:09 ` Jean Tourrilhes
2003-08-20 4:20 ` David S. Miller [this message]
2003-08-20 16:48 ` Jean Tourrilhes
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=20030819212009.36a8dc03.davem@redhat.com \
--to=davem@redhat.com \
--cc=irda-users@lists.sourceforge.net \
--cc=jt@bougret.hpl.hp.com \
--cc=jt@hpl.hp.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@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;
as well as URLs for NNTP newsgroup(s).