linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nico@fluxnic.net (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: Git pull request: shmobile fix for the vmalloc series
Date: Tue, 03 Jan 2012 09:12:42 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1201030905530.2907@xanadu.home> (raw)
In-Reply-To: <20120103095958.GJ2914@n2100.arm.linux.org.uk>

On Tue, 3 Jan 2012, Russell King - ARM Linux wrote:

> On Mon, Jan 02, 2012 at 11:34:21PM -0500, Nicolas Pitre wrote:
> > Russell, please pull the following into your devel-stable branch:
> > 
> > 	git://git.linaro.org/people/nico/linux vmalloc
> > 
> > This contains a patch from Magnus Damm fixing the oversized DMA area 
> > issue on shmobile, and a revert of the temporary and noisy workaround 
> > (which is already in your devel-stable branch) that was needed because 
> > of that issue.
> 
> Is there much point?  shmobile shows no sign of fixing their #error for
> the restart changes (and haven't responded to any of my emails)

Well, it took them 3 months before they responded to mine with a patch.  
So it would be fair to merge the fix for this one issue, even if it is 
only to remove the ugly VMALLOC_END hack from pgtable.h.

> I think we should be thinking about removing this -clearly- 
> unmaintained set of platforms.
> 
> So, it currently looks like I'm going to be pushing a #error for them
> in during the next merge window.  I'd much rather just delete the
> unmaintained code to avoid adding those evil things.

I'd vote for the #error.  My noisy #warning is possibly what created 
some motion here.


Nicolas

      reply	other threads:[~2012-01-03 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03  4:34 Git pull request: shmobile fix for the vmalloc series Nicolas Pitre
2012-01-03  9:59 ` Russell King - ARM Linux
2012-01-03 14:12   ` Nicolas Pitre [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=alpine.LFD.2.02.1201030905530.2907@xanadu.home \
    --to=nico@fluxnic.net \
    --cc=linux-arm-kernel@lists.infradead.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).