From: Markos Chandras <Markos.Chandras@imgtec.com>
To: David Miller <davem@davemloft.net>
Cc: <linux-mips@linux-mips.org>, <netdev@vger.kernel.org>,
<ast@plumgrid.com>, <dborkman@redhat.com>,
<hannes@stressinduktion.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] MIPS/BPF fixes for 4.3
Date: Fri, 5 Jun 2015 09:24:20 +0100 [thread overview]
Message-ID: <55715CB4.6020509@imgtec.com> (raw)
In-Reply-To: <20150604.114021.2198304591433879318.davem@davemloft.net>
On 06/04/2015 07:40 PM, David Miller wrote:
>
> I think your Subject meant to say "fixes for 4.2" right?
>
> Because we're currently finishing up 4.1.x and the next merge
> window will be for 4.2.x
>
Hi David,
Ralf only accepts patches for MIPS 4.2 that have been posted before
4.1-rc5. This is posted nearly before 4.1-rc7 so it's likely to go to
4.3 based on Ralf's policy. Unless of course he wants to merge that to
4.2 which would be nice of course.
--
markos
prev parent reply other threads:[~2015-06-05 8:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 10:56 [PATCH 0/6] MIPS/BPF fixes for 4.3 Markos Chandras
2015-06-04 10:56 ` [PATCH 1/6] MIPS: net: BPF: Free up some callee-saved registers Markos Chandras
2015-06-04 10:56 ` [PATCH 2/6] MIPS: net: BPF: Replace RSIZE with SZREG Markos Chandras
2015-06-04 10:56 ` [PATCH 3/6] MIPS: net: BPF: Fix stack pointer allocation Markos Chandras
2015-06-04 10:56 ` [PATCH 4/6] MIPS: net: BPF: Move register definition to the BPF header Markos Chandras
2015-06-04 10:56 ` [PATCH 5/6] MIPS: net: BPF: Use BPF register names to describe the ABI Markos Chandras
2015-06-04 10:56 ` [PATCH 6/6] MIPS: net: BPF: Introduce BPF ASM helpers Markos Chandras
2015-08-13 20:42 ` Aurelien Jarno
2015-08-14 7:59 ` Markos Chandras
2015-06-04 16:49 ` [PATCH 0/6] MIPS/BPF fixes for 4.3 Alexei Starovoitov
2015-06-05 8:26 ` Markos Chandras
2015-06-04 18:40 ` David Miller
2015-06-05 8:24 ` Markos Chandras [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=55715CB4.6020509@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.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