From: Christophe Varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: RE: Some issues noticed in my testing.
Date: Sat, 12 Feb 2005 10:40:35 +0100 [thread overview]
Message-ID: <420DCF13.3060900@free.fr> (raw)
In-Reply-To: <EA4DC661A6353747A2E5C0DE8792DDDE07C16E28@orsmsx404.amr.corp.intel.com>
ok merged.
Caushik, Ramesh wrote:
>Sorry for the delay in the response. I am resending the patch. BTW the
>code snippet that you have suggested below does not seem to take care of
>trailing whitespaces in either the vendor or product strings failing the
>match in find_hw. My suggestion is to chomp off trailing ws before doing
>the strcmp.
>
>
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2005-02-12 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 19:24 Some issues noticed in my testing Caushik, Ramesh
2005-02-12 9:40 ` Christophe Varoqui [this message]
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=420DCF13.3060900@free.fr \
--to=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.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