All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: David Howells <dhowells@redhat.com>
Cc: dhowells@redhat.com, Jonas Gorski <jonas.gorski@gmail.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: fix module.c build for 32 bit
Date: Thu, 16 Aug 2012 20:10:25 +0930	[thread overview]
Message-ID: <87a9xvce7a.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1171.1345019698@warthog.procyon.org.uk>

On Wed, 15 Aug 2012 09:34:58 +0100, David Howells <dhowells@redhat.com> wrote:
> Rusty Russell <rusty@rustcorp.com.au> wrote:
> 
> > For a build fix????
> 
> Linux hasn't pulled the asm-generic cleanup patch yet - you missed the merge
> window, I think.  Jonas detected the problem in linux-next.

Yes, I missed the window but asked Linus to pull anyway.  Was delaying
for the other module patch, left it too long.

This cleanup won't benefit from more stewing in linux-next, since it sat
there for quite a while already.  Feel free to add my Acked-by and push
it straight to Linus, otherwise I'll roll them together for next window.

Thanks,
Rusty.

WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: David Howells <dhowells@redhat.com>
Cc: Jonas Gorski <jonas.gorski@gmail.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: fix module.c build for 32 bit
Date: Thu, 16 Aug 2012 20:10:25 +0930	[thread overview]
Message-ID: <87a9xvce7a.fsf@rustcorp.com.au> (raw)
Message-ID: <20120816104025.YRtVQcBv5EkDlVNoMzGV5BtKDQwVCBxjwd8PQS40aeY@z> (raw)
In-Reply-To: <1171.1345019698@warthog.procyon.org.uk>

On Wed, 15 Aug 2012 09:34:58 +0100, David Howells <dhowells@redhat.com> wrote:
> Rusty Russell <rusty@rustcorp.com.au> wrote:
> 
> > For a build fix????
> 
> Linux hasn't pulled the asm-generic cleanup patch yet - you missed the merge
> window, I think.  Jonas detected the problem in linux-next.

Yes, I missed the window but asked Linus to pull anyway.  Was delaying
for the other module patch, left it too long.

This cleanup won't benefit from more stewing in linux-next, since it sat
there for quite a while already.  Feel free to add my Acked-by and push
it straight to Linus, otherwise I'll roll them together for next window.

Thanks,
Rusty.

  reply	other threads:[~2012-08-16 10:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  9:41 [PATCH] MIPS: fix module.c build for 32 bit Jonas Gorski
2012-08-13 15:39 ` David Howells
2012-08-14  0:12   ` Rusty Russell
2012-08-14  0:12     ` Rusty Russell
2012-08-14 14:08     ` David Howells
2012-08-14 15:13       ` [PATCH] MIPS: Fix " Ralf Baechle
2012-08-14 15:47         ` David Howells
2012-08-20  2:49         ` Rusty Russell
2012-08-15  3:21       ` [PATCH] MIPS: fix " Rusty Russell
2012-08-15  3:21         ` Rusty Russell
2012-08-15  8:34         ` David Howells
2012-08-16 10:40           ` Rusty Russell [this message]
2012-08-16 10:40             ` Rusty Russell

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=87a9xvce7a.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=dhowells@redhat.com \
    --cc=jonas.gorski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=torvalds@linux-foundation.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 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.