From: Marcel Holtmann <marcel@holtmann.org>
To: alok barsode <alokbarsode@gmail.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Using # to stringify plugin name.
Date: Tue, 21 Apr 2009 13:26:04 +0100 [thread overview]
Message-ID: <1240316764.5260.23.camel@localhost.localdomain> (raw)
In-Reply-To: <8b5debfa0904210443r2a9d0ad5ma9da78dda38046b7@mail.gmail.com>
Hi Alok,
> Here is a patch to stringify plugin name.
patch has been applied. Thanks.
Regards
Marcel
prev parent reply other threads:[~2009-04-21 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 11:43 [PATCH] Using # to stringify plugin name alok barsode
2009-04-21 12:26 ` Marcel Holtmann [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=1240316764.5260.23.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=alokbarsode@gmail.com \
--cc=linux-bluetooth@vger.kernel.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