From: Justin Chen <justin.chen@broadcom.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: linux-mips@linux-mips.org, Guenter Roeck <linux@roeck-us.net>,
Ralf Baechle <ralf@linux-mips.org>,
Florian Fainelli <f.fainelli@gmail.com>,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH] MIPS: Fix cacheinfo overflow
Date: Fri, 10 Feb 2017 15:48:04 -0800 [thread overview]
Message-ID: <23127a9b-cd2e-93be-0d1b-994890d1cb60@broadcom.com> (raw)
In-Reply-To: <20170210234437.GB9246@jhogan-linux.le.imgtec.org>
On 02/10/2017 03:44 PM, James Hogan wrote:
> Hi Justin,
>
> On Fri, Feb 10, 2017 at 03:10:47PM -0800, Justin Chen wrote:
>> I actually submitted a v2 of the patch sometime back located here:
>> https://patchwork.linux-mips.org/patch/15107/
>>
>> The v2 had some code review changes from Matt Redfearn. These changes
>> indirectly got rid of the error, which was why I wasn't running into the
>> crash.
>
> Ah yes. It looks like Ralf applied the original patch on January 3rd,
> before the last 3 submissions of the patch.
>
> Incidentally, in future I'd recommend incrementing the patch version
> number each time you submit a new version, and mentioning what has
> changed in a comment at the bottom of the commit message (anything after
> "---" gets dropped when the patch is applied).
>
> A random example:
> https://patchwork.linux-mips.org/patch/15134/
Got it. Sorry, will do next time!
>
>>
>> Either way, whatever makes more sense, we can drop the other v1 patch
>> and add v2 or just add this patch on top.
>
> Since the patch has already been applied for a while and the merge
> window is imminent, I think its best to make do with fixup patches on
> top this time around.
Sounds good to me.
>
> Thanks
> James
>
next prev parent reply other threads:[~2017-02-10 23:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 23:45 Crash in -next due to 'MIPS: Add cacheinfo support' Guenter Roeck
2017-02-10 0:01 ` Justin Chen
2017-02-10 4:50 ` Guenter Roeck
2017-02-10 9:40 ` James Hogan
2017-02-10 9:40 ` James Hogan
2017-02-10 10:39 ` James Hogan
2017-02-10 10:39 ` James Hogan
2017-02-10 17:46 ` Guenter Roeck
2017-02-10 19:15 ` Florian Fainelli
2017-02-10 22:11 ` Guenter Roeck
2017-02-10 22:39 ` James Hogan
2017-02-10 22:39 ` James Hogan
2017-02-10 22:43 ` Florian Fainelli
2017-02-10 22:48 ` Guenter Roeck
2017-02-10 13:30 ` Guenter Roeck
2017-02-10 23:01 ` [PATCH] MIPS: Fix cacheinfo overflow James Hogan
2017-02-10 23:01 ` James Hogan
2017-02-10 23:10 ` Justin Chen
2017-02-10 23:44 ` James Hogan
2017-02-10 23:44 ` James Hogan
2017-02-10 23:48 ` Justin Chen [this message]
2017-02-11 1:25 ` Guenter Roeck
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=23127a9b-cd2e-93be-0d1b-994890d1cb60@broadcom.com \
--to=justin.chen@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=linux@roeck-us.net \
--cc=ralf@linux-mips.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