All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Bastian Hecht <hechtb@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-next@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, Simon Horman <horms+renesas@verge.net.au>
Subject: Re: linux-next: manual merge of the arm-soc tree with the net-next tree
Date: Tue, 18 Jun 2013 18:36:39 +0400	[thread overview]
Message-ID: <51C07077.3040600@cogentembedded.com> (raw)
In-Reply-To: <CABYn4sx3PYBVMyio8uo-KhwprQnCmt_5k2EMaa9_EW2ud2q2nQ@mail.gmail.com>

Hello.

On 18-06-2013 12:33, Bastian Hecht wrote:

> Sergei is completely right I think. He was sceptic about the commit in
> a mail some days ago already. Unfortunately I recently haven't had
> access to my development environment to check what's up with this
> patch. I'm sorry that it ended up to you both to deal with it. I have
> written some simple bindings for the sh-eth and wanted to use it for
> our DT reference version for the Armadillo board but discarded it as I
> saw Nobuhiro Iwamatsu, the author of the sh-eth driver, cooked up some
> more mature version. I don't see them in the next branch of Simon, so
> until they appear there we can delete commit 9e0b428f079d ("ARM:

    It won't appear there. I'll just NAK it, I think I've alredy told 
Iwamatsu-san that the full blown device tree binding for this driver is 
no-go. The best we can do is use OF_DEV_AUXDATA() to rename the DT 
sourced platform device to a traditional one and assign to it the 
platform data.

> shmobile: r8a7740: Add interim sh-eth device name to clocks list")

    Unfortunately, it's now too late to just delete it at this point. I 
missed the patch unfortunately when it was just submitted.

> that is only needed for sh-eth DT usage.

> Thanks,

>   Bastian

WBR, Sergei

WARNING: multiple messages have this Message-ID (diff)
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the arm-soc tree with the net-next tree
Date: Tue, 18 Jun 2013 18:36:39 +0400	[thread overview]
Message-ID: <51C07077.3040600@cogentembedded.com> (raw)
In-Reply-To: <CABYn4sx3PYBVMyio8uo-KhwprQnCmt_5k2EMaa9_EW2ud2q2nQ@mail.gmail.com>

Hello.

On 18-06-2013 12:33, Bastian Hecht wrote:

> Sergei is completely right I think. He was sceptic about the commit in
> a mail some days ago already. Unfortunately I recently haven't had
> access to my development environment to check what's up with this
> patch. I'm sorry that it ended up to you both to deal with it. I have
> written some simple bindings for the sh-eth and wanted to use it for
> our DT reference version for the Armadillo board but discarded it as I
> saw Nobuhiro Iwamatsu, the author of the sh-eth driver, cooked up some
> more mature version. I don't see them in the next branch of Simon, so
> until they appear there we can delete commit 9e0b428f079d ("ARM:

    It won't appear there. I'll just NAK it, I think I've alredy told 
Iwamatsu-san that the full blown device tree binding for this driver is 
no-go. The best we can do is use OF_DEV_AUXDATA() to rename the DT 
sourced platform device to a traditional one and assign to it the 
platform data.

> shmobile: r8a7740: Add interim sh-eth device name to clocks list")

    Unfortunately, it's now too late to just delete it at this point. I 
missed the patch unfortunately when it was just submitted.

> that is only needed for sh-eth DT usage.

> Thanks,

>   Bastian

WBR, Sergei

  reply	other threads:[~2013-06-18 14:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  6:39 linux-next: manual merge of the arm-soc tree with the net-next tree Stephen Rothwell
2013-06-17  6:39 ` Stephen Rothwell
2013-06-17  6:39 ` Stephen Rothwell
2013-06-17 13:51 ` Sergei Shtylyov
2013-06-17 13:51   ` Sergei Shtylyov
2013-06-18  8:33   ` Bastian Hecht
2013-06-18  8:33     ` Bastian Hecht
2013-06-18 14:36     ` Sergei Shtylyov [this message]
2013-06-18 14:36       ` Sergei Shtylyov
  -- strict thread matches above, loose matches on Subject: below --
2013-07-01  6:28 Stephen Rothwell
2013-07-01  6:28 ` Stephen Rothwell
2013-07-01  6:28 ` Stephen Rothwell
2013-06-21  5:58 Stephen Rothwell
2013-06-21  5:58 ` Stephen Rothwell
2013-06-21  5:58 ` Stephen Rothwell
2013-06-21  5:49 Stephen Rothwell
2013-06-21  5:49 ` Stephen Rothwell
2013-06-21  5:49 ` Stephen Rothwell
2013-06-17  6:43 Stephen Rothwell
2013-06-17  6:43 ` Stephen Rothwell
2013-06-17  6:43 ` Stephen Rothwell
2012-11-26  9:45 Stephen Rothwell
2012-11-26  9:45 ` Stephen Rothwell
2012-11-26  9:45 ` Stephen Rothwell
2012-11-27 11:22 ` Mugunthan V N
2012-11-27 11:22   ` Mugunthan V N
2012-11-27 11:22   ` Mugunthan V N
2012-11-13  4:15 Stephen Rothwell
2012-11-13  4:15 ` Stephen Rothwell
2012-11-13  4:15 ` Stephen Rothwell
2012-11-13  7:21 ` Joachim Eastwood
2012-11-13  7:21   ` Joachim Eastwood
2012-11-13  9:08   ` Stephen Rothwell
2012-11-13  9:08     ` Stephen Rothwell

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=51C07077.3040600@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=hechtb@gmail.com \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sfr@canb.auug.org.au \
    /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.