From: Chris Ball <cjb@laptop.org>
To: Prashanth Bhat <prashanth.bhat@manipal.net>
Cc: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>, linux-mmc@vger.kernel.org
Subject: Re: Possible bug in sdio.c?
Date: Sun, 29 May 2011 11:24:51 -0400 [thread overview]
Message-ID: <m37h99pm0s.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <4DE2639C.2090200@manipal.net> (Prashanth Bhat's message of "Sun, 29 May 2011 20:47:48 +0530")
Hi,
On Sun, May 29 2011, Prashanth Bhat wrote:
> Could you please clarify the formal process for including these
> changes into the build? I have made the previous changes in my private
> code tree only so far.
See Documentation/SubmittingPatches, and send the patch you generate to
the same list of e-mail addresses you're using here.
If you have a git commit corresponding to the patch, you can use
git send-email or git format-patch to generate the patch file.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2011-05-29 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 1:56 Possible bug in sdio.c? Prashanth Bhat
2011-05-29 14:12 ` Michał Mirosław
2011-05-29 15:17 ` Prashanth Bhat
2011-05-29 15:24 ` Chris Ball [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=m37h99pm0s.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=prashanth.bhat@manipal.net \
/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).