From: "Maciej W. Rozycki" <macro@imgtec.com> To: James Hogan <james.hogan@imgtec.com> Cc: Ralf Baechle <ralf@linux-mips.org>, <linux-mips@linux-mips.org> Subject: Re: [PATCH 4/4] MIPS16e2: Provide feature overrides for non-MIPS16 systems Date: Tue, 4 Jul 2017 16:50:00 +0100 [thread overview] Message-ID: <alpine.DEB.2.00.1707041636350.3339@tp.orcam.me.uk> (raw) In-Reply-To: <20170703203250.GN31455@jhogan-linux.le.imgtec.org> On Mon, 3 Jul 2017, James Hogan wrote: > > Hardcode the absence of the MIPS16e2 ASE for all the systems that do so > > for the MIPS16 ASE already, providing for code to be optimized away. > > > > Signed-off-by: Maciej W. Rozycki <macro@imgtec.com> > > I'm inclined to agree with Florian, that git formatted patches are > slightly easier to review, perhaps they just subjectively look more > familiar. Out of interest, do you not use git for retrieving kernel > source already? I do use GIT for managing the sources themselves of course, however I keep using `quilt' for patches for two main reasons: 1. It works efficiently for the work flow I've got used to, e.g. how do I hand-edit 16th previous diff with GIT; how do I swap patches; how do I move individual hunks between patches? -- these actions are trivial with `quilt'. 2. I don't use the same system for development as I do for submissions, also to make sure no unwanted bits leak by accident. Maybe `quilt' can be taught to prepend `diffstat' automagically itself; I'll check. > Thanks for the series. Thanks for your review! Maciej
WARNING: multiple messages have this Message-ID (diff)
From: "Maciej W. Rozycki" <macro@imgtec.com> To: James Hogan <james.hogan@imgtec.com> Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org Subject: Re: [PATCH 4/4] MIPS16e2: Provide feature overrides for non-MIPS16 systems Date: Tue, 4 Jul 2017 16:50:00 +0100 [thread overview] Message-ID: <alpine.DEB.2.00.1707041636350.3339@tp.orcam.me.uk> (raw) Message-ID: <20170704155000.25E3_bnPhBRQSLWY2iWA8mDCDbOsyQt8aAkv9RNZqq4@z> (raw) In-Reply-To: <20170703203250.GN31455@jhogan-linux.le.imgtec.org> On Mon, 3 Jul 2017, James Hogan wrote: > > Hardcode the absence of the MIPS16e2 ASE for all the systems that do so > > for the MIPS16 ASE already, providing for code to be optimized away. > > > > Signed-off-by: Maciej W. Rozycki <macro@imgtec.com> > > I'm inclined to agree with Florian, that git formatted patches are > slightly easier to review, perhaps they just subjectively look more > familiar. Out of interest, do you not use git for retrieving kernel > source already? I do use GIT for managing the sources themselves of course, however I keep using `quilt' for patches for two main reasons: 1. It works efficiently for the work flow I've got used to, e.g. how do I hand-edit 16th previous diff with GIT; how do I swap patches; how do I move individual hunks between patches? -- these actions are trivial with `quilt'. 2. I don't use the same system for development as I do for submissions, also to make sure no unwanted bits leak by accident. Maybe `quilt' can be taught to prepend `diffstat' automagically itself; I'll check. > Thanks for the series. Thanks for your review! Maciej
next prev parent reply other threads:[~2017-07-04 15:50 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-05-23 12:36 [PATCH 0/4] MIPS16e2 ASE support Maciej W. Rozycki 2017-05-23 12:36 ` Maciej W. Rozycki 2017-05-23 12:37 ` [PATCH 1/4] MIPS16e2: Identify ASE presence Maciej W. Rozycki 2017-05-23 12:37 ` Maciej W. Rozycki 2017-07-03 18:32 ` James Hogan 2017-07-03 18:32 ` James Hogan 2017-05-23 12:38 ` [PATCH 2/4] MIPS16e2: Subdecode extended LWSP/SWSP instructions Maciej W. Rozycki 2017-05-23 12:38 ` Maciej W. Rozycki 2017-07-03 20:20 ` James Hogan 2017-07-03 20:20 ` James Hogan 2017-05-23 12:39 ` [PATCH 3/4] MIPS16e2: Report ASE presence in /proc/cpuinfo Maciej W. Rozycki 2017-05-23 12:39 ` Maciej W. Rozycki 2017-07-03 20:23 ` James Hogan 2017-07-03 20:23 ` James Hogan 2017-07-04 15:35 ` Maciej W. Rozycki 2017-07-04 15:35 ` Maciej W. Rozycki 2017-07-04 15:39 ` James Hogan 2017-07-04 15:39 ` James Hogan 2017-05-23 12:40 ` [PATCH 4/4] MIPS16e2: Provide feature overrides for non-MIPS16 systems Maciej W. Rozycki 2017-05-23 12:40 ` Maciej W. Rozycki 2017-05-23 19:06 ` Florian Fainelli 2017-05-23 22:21 ` Maciej W. Rozycki 2017-05-23 22:21 ` Maciej W. Rozycki 2017-07-03 20:32 ` James Hogan 2017-07-03 20:32 ` James Hogan 2017-07-04 15:50 ` Maciej W. Rozycki [this message] 2017-07-04 15:50 ` Maciej W. Rozycki 2017-07-04 16:51 ` James Hogan 2017-07-04 16:51 ` James Hogan 2017-07-03 17:22 ` [PING][PATCH 0/4] MIPS16e2 ASE support Maciej W. Rozycki 2017-07-03 17:22 ` Maciej W. Rozycki
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=alpine.DEB.2.00.1707041636350.3339@tp.orcam.me.uk \ --to=macro@imgtec.com \ --cc=james.hogan@imgtec.com \ --cc=linux-mips@linux-mips.org \ --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: linkBe 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.