linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Krause <xerofoify@gmail.com>
To: Hans-Christian Egtvedt <egtvedt@samfundet.no>
Cc: "Håvard Skinnemoen" <hskinnemoen@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] avr32: Remove unnessary variables from page.h
Date: Wed, 23 Jul 2014 11:06:01 -0400	[thread overview]
Message-ID: <CAPDOMVgXAA3dJ+x7H+BHqpc-5UNPh2X17FiCOJ6vWWWJ_b37WA@mail.gmail.com> (raw)
In-Reply-To: <20140723065013.GA15677@samfundet.no>

On Wed, Jul 23, 2014 at 2:50 AM, Hans-Christian Egtvedt
<egtvedt@samfundet.no> wrote:
> Around Wed 23 Jul 2014 02:42:36 -0400 or thereabout, Nicholas Krause wrote:
>> This removes the unneeded variables memory_start and memory_end in
>> order to fix this fix me message.
>>
>> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
>
> This is already applied to my local for-linus branch, it will be pushed once
> Linus opens up for merges after 3.16 is released.
>
>> ---
>>  arch/avr32/include/asm/page.h | 2 --
>>  1 file changed, 2 deletions(-)
>>
>> diff --git a/arch/avr32/include/asm/page.h b/arch/avr32/include/asm/page.h
>> index f805d1c..701006f 100644
>> --- a/arch/avr32/include/asm/page.h
>> +++ b/arch/avr32/include/asm/page.h
>> @@ -42,8 +42,6 @@ typedef struct page *pgtable_t;
>>  #define __pgd(x)             ((pgd_t) { (x) })
>>  #define __pgprot(x)          ((pgprot_t) { (x) })
>>
>> -/* FIXME: These should be removed soon */
>> -extern unsigned long memory_start, memory_end;
>>
>>  /* Pure 2^n version of get_order */
>>  static inline int get_order(unsigned long size)
> --
> mvh
> Hans-Christian Egtvedt


I wasn't sure if  I had sent this out. Seems I have :).
Cheers Nick

      reply	other threads:[~2014-07-23 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23  6:42 [PATCH] avr32: Remove unnessary variables from page.h Nicholas Krause
2014-07-23  6:50 ` Hans-Christian Egtvedt
2014-07-23 15:06   ` Nick 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=CAPDOMVgXAA3dJ+x7H+BHqpc-5UNPh2X17FiCOJ6vWWWJ_b37WA@mail.gmail.com \
    --to=xerofoify@gmail.com \
    --cc=egtvedt@samfundet.no \
    --cc=hskinnemoen@gmail.com \
    --cc=linux-kernel@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).