From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matt Turner <mattst88@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Firoz Khan <firoz.khan@linaro.org>,
linux-alpha <linux-alpha@vger.kernel.org>,
Richard Henderson <rth@twiddle.net>,
y2038 Mailman List <y2038@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] alpha: system call table generation support
Date: Sat, 22 Dec 2018 21:27:20 +1100 [thread overview]
Message-ID: <20181222212720.6637ef8e@canb.auug.org.au> (raw)
In-Reply-To: <CAEdQ38EY3ix6XAwAjY8H4OhFwRcT1Yuvk4ofLa_GVyh5COpkRA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
Hi Matt,
On Fri, 21 Dec 2018 11:46:59 -0500 Matt Turner <mattst88@gmail.com> wrote:
>
> Probably so. This is just a super part-time thing for me, so I've
> never figured out what I needed to do to be included in linux-next.
The requirements are:
"You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary."
Just send me an email with the URL of a git tree that has a branch that
I can fetch every day.
However, I am not doing any releases until Jan 2, so it will be
included then.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-12-22 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 9:31 [PATCH v3 0/5] alpha: system call table generation support Firoz Khan
2018-11-13 9:31 ` [PATCH v3 1/5] alpha: move __IGNORE* entries to non uapi header Firoz Khan
2018-11-13 9:31 ` [PATCH v3 2/5] alpha: remove CONFIG_OSF4_COMPAT flag from syscall table Firoz Khan
2018-11-13 9:31 ` [PATCH v3 3/5] alpha: add __NR_syscalls along with NR_SYSCALLS Firoz Khan
2018-11-13 9:31 ` [PATCH v3 4/5] alpha: add system call table generation support Firoz Khan
2018-11-13 9:31 ` [PATCH v3 5/5] alpha: generate uapi header and syscall table header files Firoz Khan
2018-12-14 15:17 ` [PATCH v3 0/5] alpha: system call table generation support Firoz Khan
2018-12-19 15:59 ` Matt Turner
2018-12-19 17:08 ` Arnd Bergmann
2018-12-21 16:46 ` Matt Turner
2018-12-22 10:27 ` Stephen Rothwell [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=20181222212720.6637ef8e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=firoz.khan@linaro.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.net \
--cc=y2038@lists.linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.