All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms+renesas@verge.net.au>,
	dmaengine@vger.kernel.org,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH] dmaengine: rcar-dmac: Document SoC specific bindings
Date: Mon, 18 Jan 2016 14:49:32 +0000	[thread overview]
Message-ID: <20160118143731.GQ11130@localhost> (raw)
In-Reply-To: <CAMuHMdXVBSjTb_-7o4rDh_S+i64QKEr-5KUnSfd3Nqt1D1TE2Q@mail.gmail.com>

On Thu, Jan 14, 2016 at 11:09:47AM +0100, Geert Uytterhoeven wrote:
> Hi Vinod,
> 
> On Mon, Nov 16, 2015 at 4:55 AM, Vinod Koul <vinod.koul@intel.com> wrote:
> > On Thu, Nov 12, 2015 at 10:53:59AM +0900, Simon Horman wrote:
> >> In general Renesas hardware is not documented to the extent where the
> >> relationship between IP blocks on different SoCs can be assumed although
> >> they may appear to operate the same way. Furthermore the documentation
> >> typically does not specify a version for individual IP blocks. For these
> >> reasons a convention of using the SoC name in place of a version and
> >> providing SoC-specific compat strings has been adopted.
> >>
> >> Although not universally liked this convention is used in the bindings for
> >> most drivers for Renesas hardware. The purpose of this patch is to
> >> update the Renesas R-Car DMA Controller driver to follow this convention.
> >
> > Applied, thanks
> 
> This patch (and this patch only) has disappeared from your next branch between
> January 6 and 7, and thus wasn't included in your pull request for v4.5.
> 
> Was there a specific reason for that, or was it just an oversight?
> 
> Note that the added compatible values in in use (in arm-soc/for-next).


Hi Geert,

That only means I messed up. I apply patches to for-linus or topic branches
and then merge all topics to for-linus and send that to Linus.

In this case I didn't see this in any of the topics or for-linus which means
I applied to next which I usually trash and keep rebuiling on latest -rc.

Now git helped me track this commit on a deleted branch (which reminds us
what a wonderful thing git is... screwed up, dont worrry git is our
superhero to rescue).

I have cherry-picked this patch and applied to for-4.5 branch and will
send to Linus in few days along with few more fixes.

Thanks for reporting
-- 
~Vinod

WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms+renesas@verge.net.au>,
	dmaengine@vger.kernel.org,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH] dmaengine: rcar-dmac: Document SoC specific bindings
Date: Mon, 18 Jan 2016 20:07:32 +0530	[thread overview]
Message-ID: <20160118143731.GQ11130@localhost> (raw)
In-Reply-To: <CAMuHMdXVBSjTb_-7o4rDh_S+i64QKEr-5KUnSfd3Nqt1D1TE2Q@mail.gmail.com>

On Thu, Jan 14, 2016 at 11:09:47AM +0100, Geert Uytterhoeven wrote:
> Hi Vinod,
> 
> On Mon, Nov 16, 2015 at 4:55 AM, Vinod Koul <vinod.koul@intel.com> wrote:
> > On Thu, Nov 12, 2015 at 10:53:59AM +0900, Simon Horman wrote:
> >> In general Renesas hardware is not documented to the extent where the
> >> relationship between IP blocks on different SoCs can be assumed although
> >> they may appear to operate the same way. Furthermore the documentation
> >> typically does not specify a version for individual IP blocks. For these
> >> reasons a convention of using the SoC name in place of a version and
> >> providing SoC-specific compat strings has been adopted.
> >>
> >> Although not universally liked this convention is used in the bindings for
> >> most drivers for Renesas hardware. The purpose of this patch is to
> >> update the Renesas R-Car DMA Controller driver to follow this convention.
> >
> > Applied, thanks
> 
> This patch (and this patch only) has disappeared from your next branch between
> January 6 and 7, and thus wasn't included in your pull request for v4.5.
> 
> Was there a specific reason for that, or was it just an oversight?
> 
> Note that the added compatible values in in use (in arm-soc/for-next).


Hi Geert,

That only means I messed up. I apply patches to for-linus or topic branches
and then merge all topics to for-linus and send that to Linus.

In this case I didn't see this in any of the topics or for-linus which means
I applied to next which I usually trash and keep rebuiling on latest -rc.

Now git helped me track this commit on a deleted branch (which reminds us
what a wonderful thing git is... screwed up, dont worrry git is our
superhero to rescue).

I have cherry-picked this patch and applied to for-4.5 branch and will
send to Linus in few days along with few more fixes.

Thanks for reporting
-- 
~Vinod

  reply	other threads:[~2016-01-18 14:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12  1:53 [PATCH] dmaengine: rcar-dmac: Document SoC specific bindings Simon Horman
2015-11-12  1:53 ` Simon Horman
2015-11-12 10:25 ` Geert Uytterhoeven
2015-11-12 10:25   ` Geert Uytterhoeven
2015-11-12 23:28 ` Rob Herring
2015-11-12 23:28   ` Rob Herring
2015-11-13  8:08   ` Geert Uytterhoeven
2015-11-13  8:08     ` Geert Uytterhoeven
2015-11-16  3:51 ` Vinod Koul
2015-11-16  3:55   ` Vinod Koul
2016-01-14 10:09   ` Geert Uytterhoeven
2016-01-14 10:09     ` Geert Uytterhoeven
2016-01-18 14:37     ` Vinod Koul [this message]
2016-01-18 14:49       ` Vinod Koul
2016-01-18 14:46       ` Geert Uytterhoeven

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=20160118143731.GQ11130@localhost \
    --to=vinod.koul@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=horms+renesas@verge.net.au \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@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 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.