From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] bus: brcmstb_gisb: misc fixes
Date: Fri, 10 Oct 2014 23:10:22 +0200 [thread overview]
Message-ID: <1956888.MIJ5XMTDdo@wuerfel> (raw)
In-Reply-To: <5438329D.1040600@gmail.com>
On Friday 10 October 2014 12:25:17 Florian Fainelli wrote:
>
> On 09/22/2014 11:02 AM, Florian Fainelli wrote:
> > Hi Arnd,
> >
> > This patch set contains two small fixes for the Broadcom GISB bus
> > arbiter code. First patch makes sure we do register a fault code for
> > ARM platforms, second patch is a fix when the code is used on a PM
> > capable system.
>
> Once the merge window re-opens in about a week from now, how do you want
> me to submit those patches? Do you want them as part of a brcmstb pull
> request, or something else?
At least one of us is confused. The merge window is currently open,
and I have send all outstanding pull requests for 3.18. If you have
bug fixes that are required for 3.18, we should merge them now and
send them as soon as possible.
If this is stuff that can wait for 3.19, please send a pull
request after the the end of the ELC/LPC conferences next week
so we can queue it up in next/fixes-non-critical.
Arnd
next prev parent reply other threads:[~2014-10-10 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 18:02 [PATCH v3 0/2] bus: brcmstb_gisb: misc fixes Florian Fainelli
2014-09-22 18:02 ` [PATCH v3 1/2] bus: brcmstb_gisb: register the fault code hook Florian Fainelli
2014-09-22 18:02 ` [PATCH v3 2/2] bus: brcmstb_gisb: save and restore GISB timeout Florian Fainelli
2014-10-10 19:25 ` [PATCH v3 0/2] bus: brcmstb_gisb: misc fixes Florian Fainelli
2014-10-10 21:10 ` Arnd Bergmann [this message]
2014-10-10 21:55 ` Florian Fainelli
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=1956888.MIJ5XMTDdo@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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