From: Daniel Ng <daniel.ng1234@gmail.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: How to submit patches?
Date: Fri, 27 Mar 2009 17:49:27 +1100 [thread overview]
Message-ID: <547eba1b0903262349ne434f33of96c0a31a452f2af@mail.gmail.com> (raw)
Hi,
What are the current requirements for submitting a patch?
I have created a patch which provides an SPI_LSB_FIRST option for the
SPI Bit-banging driver.
The SPI Bit-banging driver currently only supports MSB-first data
transmission (see include/linux/spi/spi_bitbang.h).
If someone could point me to the relevant, current documentation for
submitting kernel driver patches, I'd be most appreciative.
Cheers,
Daniel
next reply other threads:[~2009-03-27 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 6:49 Daniel Ng [this message]
2009-03-27 6:55 ` How to submit patches? Stephen Rothwell
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=547eba1b0903262349ne434f33of96c0a31a452f2af@mail.gmail.com \
--to=daniel.ng1234@gmail.com \
--cc=linuxppc-dev@ozlabs.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