From: Ralf Baechle <ralf@linux-mips.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: [PATCH] MIPS: BCM47XX: Make bcma init NVRAM instead of bcm47xx polling it
Date: Tue, 28 Oct 2014 15:13:44 +0100 [thread overview]
Message-ID: <20141028141344.GG16320@linux-mips.org> (raw)
In-Reply-To: <CACna6rzJfJGwHP62ru=c3M0CcfrJZa7aUhMn0JQym7RgxwgPAA@mail.gmail.com>
On Tue, Oct 28, 2014 at 02:46:30PM +0100, Rafał Miłecki wrote:
> Thank you! To avoid similar confusion in the future, I've created
> patchwork account that will allow me to mark old (superseded) patches.
Yes, I wish everybody would do that. Would save me from the daily heart
attack when I open patchwork and see 2.71 metric gazillion patches pending -
only to later find out that half of them were superseeded by later
revision!
It's also useful in case a submitter has multiple email addresses. It
allows to search for one address and find all submissions.
> In case you find time to push two more pending BCM47XX patches, it
> would be great to see them in your tree.
>
> 1) [V2] MIPS: BCM47XX: Move SPROM fallback code into sprom.c
> http://patchwork.linux-mips.org/patch/8232/
> It's a rebased version of patch sent ~2 months ago (7617) that was
> Acked-by Hauke
>
> 2) MIPS: BCM47XX: Initialize bcma bus later (with mm available)
> http://patchwork.linux-mips.org/patch/8234/
> It's resend-ing of RFC patch (7606) that also was Acked-by Hauke.
Both applied and pushed.
Ralf
next prev parent reply other threads:[~2014-10-28 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 12:30 [PATCH] MIPS: BCM47XX: Make bcma init NVRAM instead of bcm47xx polling it Rafał Miłecki
2014-10-28 12:48 ` Ralf Baechle
2014-10-28 12:51 ` Rafał Miłecki
2014-10-28 13:13 ` Ralf Baechle
2014-10-28 13:18 ` Rafał Miłecki
2014-10-28 13:26 ` Ralf Baechle
2014-10-28 13:46 ` Rafał Miłecki
2014-10-28 13:55 ` Ralf Baechle
2014-10-28 14:13 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-03 11:32 Rafał Miłecki
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=20141028141344.GG16320@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=hauke@hauke-m.de \
--cc=linux-mips@linux-mips.org \
--cc=zajec5@gmail.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 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.