mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: linux-kernel@vger.kernel.org, fengguang.wu@intel.com
Subject: Re: [PATCH] m32r: add simple dma
Date: Thu, 20 Oct 2016 20:29:18 -0700	[thread overview]
Message-ID: <20161020202918.b7cb3fe24058addddabb7534@linux-foundation.org> (raw)
In-Reply-To: <1475949198-31623-1-git-send-email-sudipm.mukherjee@gmail.com>

On Sat,  8 Oct 2016 23:23:18 +0530 Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:

> Some builds of m32r were failing as it tried to build few drivers which
> needed dma but m32r is not having dma support. Objections were raised
> when it was tried to make those drivers depend on HAS_DMA.

Huh.  What were these objections?  That sounds like the appropriate
fix.  And I suggest that a summary of those objections be captured in
this patch's changelog.

> So the next
> best thing is to add dma support to m32r.
> dma_noop is a very simple dma with 1:1 memory mapping.
> 
> Signed-off-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
> ---
> 
> Hi Andrew,
> Just to let you know that this was not tested on any board. I think I
> have told you earlier that inspite of all  my efforts I could not find
>  any source of information to procure a board of m32r.

It is a worry.  We're saying "m32r linux now supports these drivers",
only we don't know if that is true.

> Hi Fengguang,
> If Andrew accepts this patch then it will open pandora's box as lots of
> other drivers which were never build for m32r will be built now and you
> are going to gets lots and lots of new build warnings. But nothing
> breaks.

  reply	other threads:[~2016-10-21  3:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-08 17:53 Sudip Mukherjee
2016-10-21  3:29 ` Andrew Morton [this message]
2016-10-30 18:17   ` Sudip Mukherjee
2016-11-03 19:13     ` Andrew Morton
2016-11-08 20:07       ` Sudip Mukherjee

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=20161020202918.b7cb3fe24058addddabb7534@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudipm.mukherjee@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome