From: Willy Tarreau <w@1wt.eu>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Willy Tarreau <willy@meta-x.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: panel: remove duplicate code
Date: Tue, 7 Apr 2015 16:33:24 +0200 [thread overview]
Message-ID: <20150407143324.GD17557@1wt.eu> (raw)
In-Reply-To: <20150407142117.GA31260@sudip-PC>
On Tue, Apr 07, 2015 at 07:51:17PM +0530, Sudip Mukherjee wrote:
> On Tue, Apr 07, 2015 at 04:14:59PM +0200, Willy Tarreau wrote:
> > Not-so-old laptops used to have parport connectors for a while, and can be
> > found at a very cheap price or even for free by now with dead batteries.
> free laptop sounds good.. :)
> where can i get some?
Friends replacing theirs in general, or your employer's dead stock :-)
> > If you want to run on your PC, you'll have to order a PCIe parallel port NIC
s/NIC/card above
> > I guess.
> i already have pc with parallel port, and on that i check your panel
> codes before sending. but here we were discussing about the required
> hardware to test ppscsi module.
Ah sorry for being out of topic then, I missed this point, I thought
it was for PP in general.
Regards,
Willy
next prev parent reply other threads:[~2015-04-07 14:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 8:25 [PATCH] staging: panel: remove duplicate code Sudip Mukherjee
2015-04-07 8:49 ` Dan Carpenter
2015-04-07 9:25 ` Sudip Mukherjee
2015-04-07 9:44 ` Greg Kroah-Hartman
2015-04-07 9:56 ` Sudip Mukherjee
2015-04-07 10:12 ` Greg Kroah-Hartman
2015-04-07 14:14 ` Willy Tarreau
2015-04-07 14:21 ` Sudip Mukherjee
2015-04-07 14:33 ` Willy Tarreau [this message]
2015-04-07 14:41 ` Sudip Mukherjee
2015-04-07 9:45 ` Dan Carpenter
2015-04-07 10:36 ` Sudip Mukherjee
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=20150407143324.GD17557@1wt.eu \
--to=w@1wt.eu \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=willy@meta-x.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).