From: Stephen Hemminger <shemminger@osdl.org>
To: Samuel Ortiz <samuel@sortiz.org>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, irda-users@lists.sourceforge.net,
hch@lst.de
Subject: Re: [PATCH 3/4] [IrDA] stir4200, switching to the kthread API
Date: Thu, 25 May 2006 11:01:54 -0700 [thread overview]
Message-ID: <20060525110154.32084ca6@localhost.localdomain> (raw)
In-Reply-To: <20060525061944.GC24611@sortiz.org>
On Thu, 25 May 2006 06:19:44 +0000
Samuel Ortiz <samuel@sortiz.org> wrote:
> stir4200 uses a kernel thread for its TX/RX operations, and it is now
> converted to the kernel kthread API.
> Tested on an STIR4200 based dongle.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Samuel Ortiz <samuel@sortiz.org>
>
Looks fine.
next prev parent reply other threads:[~2006-05-25 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 6:19 [PATCH 3/4] [IrDA] stir4200, switching to the kthread API Samuel Ortiz
2006-05-25 18:01 ` Stephen Hemminger [this message]
2006-05-25 23:20 ` David Miller
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=20060525110154.32084ca6@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=irda-users@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=samuel@sortiz.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).