From: Rich Felker <dalias@libc.org>
To: linux-sh@vger.kernel.org
Subject: Re: sh7724 regression: commit 8222dbe21e79338de92d5e1956cd1e3994cc9f93
Date: Thu, 17 Mar 2016 17:38:40 +0000 [thread overview]
Message-ID: <20160317173840.GG21636@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAMuHMdWR0RZhGrX4qW+fHwOYxAXffNinUdhrL=SZsMn5BUKoeA@mail.gmail.com>
On Wed, Mar 16, 2016 at 08:35:20PM -0400, Rich Felker wrote:
> On Sun, Mar 13, 2016 at 03:08:42PM -0400, Rich Felker wrote:
> > On Fri, Mar 11, 2016 at 12:06:22PM +0100, David Hildenbrand wrote:
> > >
> > > > > > That fixes it for me:
> > > > > >
> > > > > > Tested-by: Hans Verkuil <hans.verkuil@cisco.com>
> > > > > >
> > > > > > BTW, your patch is garbled and I had to manually make the change (not a big
> > > > > > deal for a simple change like this).
> > > > > >
> > > > >
> > > > > Thanks for testing. I just copy-pasted the patch, so this was somehow
> > > > > expected :)
> > > > >
> > > > > @maintainers, how to proceed with this? Shall I send that patch again directly
> > > > > to the linux-sh list?
> > > > >
> > > > > David
> > > >
> > >
> > > How to proceed with this patch? Anyone?
> >
> > Sorry for not getting you a response sooner. I don't yet have the
> > hardware to test this fix on (would like to find some), but it looks
> > reasonable to me and like it doesn't risk introducing other
> > regressions. Sato-san, do you have any thoughts or objections to the
> > patch?
>
> Can you follow up with a well-formed patch that I can apply. No
> promises since I'm new to kernel maintainership workflow but I'll try
> to get it in this merge window if I can.
I was able to clean it up (looks like terminal copy&paste just botched
all the spaces) so I'm applying it to my tree, since it seems likely
that most SH models with MMU are broken without it. Thanks!
Rich
next prev parent reply other threads:[~2016-03-17 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 14:20 sh7724 regression: commit 8222dbe21e79338de92d5e1956cd1e3994cc9f93 Geert Uytterhoeven
2016-02-27 14:28 ` John Paul Adrian Glaubitz
2016-02-27 14:33 ` Hans Verkuil
2016-02-29 8:24 ` David Hildenbrand
2016-02-29 9:01 ` Hans Verkuil
2016-02-29 11:03 ` David Hildenbrand
2016-03-02 0:20 ` Simon Horman
2016-03-11 11:06 ` David Hildenbrand
2016-03-13 19:08 ` Rich Felker
2016-03-17 0:35 ` Rich Felker
2016-03-17 17:38 ` Rich Felker [this message]
2016-03-29 6:33 ` David Hildenbrand
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=20160317173840.GG21636@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=linux-sh@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).