From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Paul Bolle <pebolle@tiscali.nl>, Ralf Baechle <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>
Subject: Re: MIPS: Remove last traces of SMTC Support too?
Date: Wed, 9 Apr 2014 09:58:38 +0100 [thread overview]
Message-ID: <53450BBE.7050501@imgtec.com> (raw)
In-Reply-To: <1397033309.22767.8.camel@x220>
On 04/09/2014 09:48 AM, Paul Bolle wrote:
> The patch "MIPS: Remove SMTC Support" landed in linux-next (see
> next-20140409). A quick grep of the tree suggests a follow up is needed
> (a sort-of-patch is pasted below).
>
> Is a similar follow up queued somewhere? If not, should I submit a patch
> or should I wait with doing that until "MIPS: Remove SMTC Support" hits
> mainline?
>
>
> Paul Bolle
Hi Paul,
I talked to Ralf yesterday. It seems the patch was not applied correctly
and there are a few traces left. My original patch definitely removes
the traces listed in your patch.
You can compare the original patch
https://patchwork.linux-mips.org/patch/6719/
with the one currently present in upstream-sfr/mips-for-linux-next branch
--
markos
WARNING: multiple messages have this Message-ID (diff)
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Paul Bolle <pebolle@tiscali.nl>, Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS: Remove last traces of SMTC Support too?
Date: Wed, 9 Apr 2014 09:58:38 +0100 [thread overview]
Message-ID: <53450BBE.7050501@imgtec.com> (raw)
Message-ID: <20140409085838.Jt3tiheOD1zXgPbCQaKrij2UHP6Y2oWAXHqZPRcTEg8@z> (raw)
In-Reply-To: <1397033309.22767.8.camel@x220>
On 04/09/2014 09:48 AM, Paul Bolle wrote:
> The patch "MIPS: Remove SMTC Support" landed in linux-next (see
> next-20140409). A quick grep of the tree suggests a follow up is needed
> (a sort-of-patch is pasted below).
>
> Is a similar follow up queued somewhere? If not, should I submit a patch
> or should I wait with doing that until "MIPS: Remove SMTC Support" hits
> mainline?
>
>
> Paul Bolle
Hi Paul,
I talked to Ralf yesterday. It seems the patch was not applied correctly
and there are a few traces left. My original patch definitely removes
the traces listed in your patch.
You can compare the original patch
https://patchwork.linux-mips.org/patch/6719/
with the one currently present in upstream-sfr/mips-for-linux-next branch
--
markos
next prev parent reply other threads:[~2014-04-09 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 8:48 MIPS: Remove last traces of SMTC Support too? Paul Bolle
2014-04-09 8:58 ` Markos Chandras [this message]
2014-04-09 8:58 ` Markos Chandras
2014-04-09 9:01 ` James Hogan
2014-04-09 9:01 ` James Hogan
2014-04-09 9:03 ` Paul Bolle
2014-04-09 9:10 ` Markos Chandras
2014-04-09 9:10 ` Markos Chandras
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=53450BBE.7050501@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=pebolle@tiscali.nl \
--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 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.