From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Thomas Huth <thuth@redhat.com>
Subject: [PATCH slof] README: Update with patch submittion note
Date: Mon, 6 Jul 2015 14:09:10 +1000 [thread overview]
Message-ID: <1436155750-16815-1-git-send-email-aik@ozlabs.ru> (raw)
This adds a maillist and emails to be used when posting a patch for SLOF.
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Thomas Huth <thuth@redhat.com>
Cc: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
---
I was asked to describe somewhere how to post new patches so this is the first
attempt. Please fix my english and add/remove personal emails and any other
comments are also welcome. Thanks!
---
README | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/README b/README
index 58e9294..b81fd08 100644
--- a/README
+++ b/README
@@ -11,6 +11,7 @@ Index
2.2 Overview of the source code
2.4 Extending the Forth engine
3.0 Limitations
+4.0 Submitting patches
1.0 Introduction to Slimline Open Firmware
@@ -236,6 +237,15 @@ To add primitives:
On a JS21 all memory configurations should work.
+4.0 Submitting patches
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+Patches for SLOF should be made against https://github.com/aik/SLOF,
+the master branch and posted to linuxppc-dev@ozlabs.org. It is
+recommended also cc: to aik@ozlabs.ru, nikunj@linux.vnet.ibm.com,
+thuth@redhat.com.
+
+
Documentation
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--
2.4.0.rc3.8.gfb3e7d5
next reply other threads:[~2015-07-06 4:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 4:09 Alexey Kardashevskiy [this message]
2015-07-06 5:03 ` [PATCH slof] README: Update with patch submittion note Nikunj A Dadhania
2015-07-06 7:22 ` Thomas Huth
2015-07-06 8:02 ` Alexey Kardashevskiy
2015-07-06 8:14 ` Thomas Huth
2015-07-06 8:29 ` Nikunj A Dadhania
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=1436155750-16815-1-git-send-email-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=thuth@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;
as well as URLs for NNTP newsgroup(s).