From: "Kiran, Pichika Uday" <pichika.uday.kiran@intel.com>
To: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Cc: "Nallani, Prasad" <prasad.nallani@intel.com>,
"Kunche, Kishore" <kishore.kunche@intel.com>
Subject: Contribution towards LibFFI development
Date: Mon, 17 Jun 2019 09:35:00 -0000 [thread overview]
Message-ID: <6282B4CB3C7A4A45BCD404004B58DECB58E40A@BGSMSX101.gar.corp.intel.com> (raw)
Hello Team,
Myself Uday Kiran from Intel decided to contribute to libffi development and bug fixing.
Can someone please help me in providing the below details on libffi which will help me to understand the library better.
1. How to setup the multiple platforms to check the bugs raised in github
2. Is CI(Continuous integration) process happenings for libffi ? If yes, what is the frequency of this and who is the maintainer ?
3. How to verify if any fix has been made by running bunch of test cases in-order not to disturb the existing functionality.
Along with the above details, can someone please send me the documentation on libffi and its code flow ?
Looking forward for the responses.
Thanks & Regards
Uday Kiran
next reply other threads:[~2019-06-17 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 9:35 Kiran, Pichika Uday [this message]
[not found] ` <87tvco30m8.fsf@laptop.atgreen.org>
2019-06-18 14:05 ` Kiran, Pichika Uday
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=6282B4CB3C7A4A45BCD404004B58DECB58E40A@BGSMSX101.gar.corp.intel.com \
--to=pichika.uday.kiran@intel.com \
--cc=kishore.kunche@intel.com \
--cc=libffi-discuss@sourceware.org \
--cc=prasad.nallani@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).