public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Nick Krause <xerofoify@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	David Miller <davem@davemloft.net>,
	sparclinux@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Sparc: Fix Mes in highmem.c
Date: Fri, 18 Jul 2014 20:20:29 +0200	[thread overview]
Message-ID: <20140718182028.GA21570@ravnborg.org> (raw)
In-Reply-To: <CAPDOMVji-rOr4OT0M+RX0XaKLsscH_PJ8Q0BEw3xyp34KjHOKA@mail.gmail.com>

On Fri, Jul 18, 2014 at 01:06:41PM -0400, Nick Krause wrote:
> On Fri, Jul 18, 2014 at 10:08 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Thu, Jul 17, 2014 at 11:05:12PM -0400, Nick Krause wrote:
> >> On Thu, Jul 17, 2014 at 1:38 PM, Nick Krause <xerofoify@gmail.com> wrote:
> >> > On Thu, Jul 17, 2014 at 3:52 AM, Sam Ravnborg <sam@ravnborg.org> wrote:
> >> >> On Wed, Jul 16, 2014 at 10:25:30PM -0400, Nick Krause wrote:
> >> >>> I am hitting three Fix mes in this file and am wondering as the
> >> >>> maintainer how you would like
> >> >>> to clean them up.
> >> >>
> >> >> They may be addressed if we one day decide to give the sparc32 highmem
> >> >> support a big overhaul. Until then they are left as is.
> >> >>
> >> >>         Sam
> >> >  Very well then I will just not touch it until we are going to
> >> > overhaul the highmem  for
> >> > sparc32.
> >> > Cheers Nick
> >> If you want I can fix the sparc32 highmem area with your help. I am new
> >> to the kernel so a little help if needed would be great when doing this work
> >> for you:).
> >
> > It will take a bit more than a "little help" to do such a task. Among other
> > things, owning a sparc32 box is one of them. Do you happen to have one?
> > Or do you have access to one?
> >
> > -- Steve
> >
> 
> I understand that I don't have a sparc32 box , however if someone can
> test my fixes for me this
> may work.
No it will not work.
This is as many other areas something that require some knowledge plus
some trial-and-error to do.

You should understand that things takes time to learn before you can go hacking
around in stuff. And highmem support in sparc32 is one such area.
Time are in some areas counted in months and in other areas counted in years.
This is not some simple userspace program - please try to understand this.

	Sam

  reply	other threads:[~2014-07-18 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17  2:25 Sparc: Fix Mes in highmem.c Nick Krause
2014-07-17  7:52 ` Sam Ravnborg
2014-07-17 17:38   ` Nick Krause
2014-07-18  3:05     ` Nick Krause
2014-07-18  7:37       ` Sam Ravnborg
2014-07-18 14:08       ` Steven Rostedt
2014-07-18 17:06         ` Nick Krause
2014-07-18 18:20           ` Sam Ravnborg [this message]
2014-07-18 19:51             ` Nick Krause

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=20140718182028.GA21570@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=xerofoify@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox