From: Sam Ravnborg <sam@ravnborg.org>
To: Nick Krause <xerofoify@gmail.com>
Cc: 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 07:37:59 +0000 [thread overview]
Message-ID: <20140718073758.GA20028@ravnborg.org> (raw)
In-Reply-To: <CAPDOMVj9GcoC26Sp6sOmwZf39mfOn=Wy87AnfzDguthcFOTXhg@mail.gmail.com>
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.
This is not just something that one can jump on fixing.
Sam
WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Nick Krause <xerofoify@gmail.com>
Cc: 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 09:37:59 +0200 [thread overview]
Message-ID: <20140718073758.GA20028@ravnborg.org> (raw)
In-Reply-To: <CAPDOMVj9GcoC26Sp6sOmwZf39mfOn=Wy87AnfzDguthcFOTXhg@mail.gmail.com>
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.
This is not just something that one can jump on fixing.
Sam
next prev parent reply other threads:[~2014-07-18 7:37 UTC|newest]
Thread overview: 18+ 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 2:25 ` Nick Krause
2014-07-17 7:52 ` Sam Ravnborg
2014-07-17 7:52 ` Sam Ravnborg
2014-07-17 17:38 ` Nick Krause
2014-07-17 17:38 ` Nick Krause
2014-07-18 3:05 ` Nick Krause
2014-07-18 3:05 ` Nick Krause
2014-07-18 7:37 ` Sam Ravnborg [this message]
2014-07-18 7:37 ` Sam Ravnborg
2014-07-18 14:08 ` Steven Rostedt
2014-07-18 14:08 ` Steven Rostedt
2014-07-18 17:06 ` Nick Krause
2014-07-18 17:06 ` Nick Krause
2014-07-18 18:20 ` Sam Ravnborg
2014-07-18 18:20 ` Sam Ravnborg
2014-07-18 19:51 ` Nick Krause
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=20140718073758.GA20028@ravnborg.org \
--to=sam@ravnborg.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.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 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.