Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Nicholas Krause <xerofoify@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: akpm@linux-foundation.org, kumba@gentoo.org,
	linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] mips:Fix build error for ip32_defconfig configuration
Date: Fri, 15 May 2015 16:51:43 -0400	[thread overview]
Message-ID: <97052E66-F758-4D28-ABD7-8564E26CB9FF@gmail.com> (raw)
In-Reply-To: <20150515204546.GH2322@linux-mips.org>



On May 15, 2015 4:45:46 PM EDT, Ralf Baechle <ralf@linux-mips.org> wrote:
>On Fri, May 15, 2015 at 04:16:59PM -0400, nick wrote:
>
>> On 2015-05-15 04:10 PM, Ralf Baechle wrote:
>> > On Thu, May 14, 2015 at 10:20:17AM -0400, Nicholas Krause wrote:
>> > 
>> >> This fixes the make error when building the ip32_defconfig
>> >> configuration due to using sgio2_cmos_devinit rather then
>> >> the correct function,sgio2_rtc_devinit in a device_initcall
>> >> below this function's definition.
>> > 
>> > I've already applied Joshua Kinard's 
>> > https://patchwork.linux-mips.org/patch/9787/ with a minor cosmetic
>> > touchup.
>> > 
>> >   Ralf
>> > 
>> Ralf,
>> As you may already known my rep with the other kernel developers is
>pretty bad.
>> Based off this work can you try(time permitting) to put it a good
>word that I am
>> improving.
>
>The kernel world is a meritocracy.  Which means your status will depend
>on the value of your contributions.  So I think there's not much I
>could
>or should do but to let your merrits aka patches speak for themselves.
>
>  Ralf
Very well then thanks anyway. 
Nick 

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

      reply	other threads:[~2015-05-15 20:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 14:20 [PATCH RESEND] mips:Fix build error for ip32_defconfig configuration Nicholas Krause
2015-05-15 20:10 ` Ralf Baechle
2015-05-15 20:16   ` nick
2015-05-15 20:45     ` Ralf Baechle
2015-05-15 20:51       ` Nicholas Krause [this message]

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=97052E66-F758-4D28-ABD7-8564E26CB9FF@gmail.com \
    --to=xerofoify@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=kumba@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --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: 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