public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-ppc4xx/next
Date: Fri, 13 Nov 2009 15:27:01 +0100	[thread overview]
Message-ID: <4AFD6CB5.8080807@denx.de> (raw)
In-Reply-To: <200911120614.04989.sr@denx.de>

Hi Stefan,

Stefan Roese wrote:
> Hi Matthias,
> 
> On Wednesday 11 November 2009 22:12:06 Matthias Fuchs wrote:
>>> please pull some updates for "next". Thanks.
>>>
>>>
>>> The following changes since commit
>>> cd12f615e4dd1dd24caab93f4157894783c6c1c0: Wolfgang Grandegger (1):
>>>         mpc52xx: add support for the IPEK01 board
>>>
>>> are available in the git repository at:
>>>
>>>   git://www.denx.de/git/u-boot-ppc4xx.git next
>>>
>>> Matthias Fuchs (1):
>>>       ppc4xx: Add UBI support to PLU405 boards
>> What happened to the others? ".. init coupler..." etc.
> 
> As you know, these patches depend on the sja1000 CAN header:
> 
> [PATCH 1/2] Add minimal SJA1000 header for basic CAN mode
> 
> And I'm not sure what the current status of this header is. Wolfgang 
> Grandegger (added to Cc) also introduced some new CAN stuff. We don't want to 
> add multiple headers of course.

My stuff was sent as RFC. It's on hold now as there was little feedback.

> So how should we continue here? I understand that your patches depending on 
> this sja1000 header are bugfixes:
> 
> [PATCH 2/2 V3] ppc4xx: Initialize magnetic couplers in PLU405
> [PATCH] ppc4xx: Initialize magnetic coupler on VOM405 boards
> 
> And you introduced this header on the explicit proposal from Wolfgang Denk. So 
> I would vote for adding your bug fix patches with your sja1000 header right 
> now. We should remove this header again, when the CAN support from Wolfgang 
> Grandegger hits mainline.

Yep.

Wolfgang.

  reply	other threads:[~2009-11-13 14:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 15:41 [U-Boot] Please pull u-boot-ppc4xx/next Stefan Roese
2009-11-11 21:12 ` Matthias Fuchs
2009-11-12  5:14   ` Stefan Roese
2009-11-13 14:27     ` Wolfgang Grandegger [this message]
2009-11-11 22:07 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2012-10-02 13:36 Stefan Roese
2012-10-02 17:55 ` Tom Rini
2012-10-03  0:15 ` Marek Vasut
2012-10-04  7:23   ` Stefan Roese
2012-10-04 23:19     ` Marek Vasut
2010-12-17 10:15 Stefan Roese
2010-12-17 19:11 ` Wolfgang Denk
2010-09-22  9:14 Stefan Roese
2010-09-22 21:01 ` Wolfgang Denk
2010-09-23  7:12   ` Stefan Roese
2010-09-23 19:07 ` Wolfgang Denk
2009-11-25 10:00 Stefan Roese
2009-12-01 10:54 ` Wolfgang Denk
2009-11-23 15:28 Stefan Roese
2009-11-24 22:14 ` Wolfgang Denk
2009-11-25  9:56   ` Stefan Roese
2009-11-19 10:45 Stefan Roese
2009-11-21 22:15 ` Wolfgang Denk
2009-05-28 11:22 Stefan Roese
2009-05-28 19:36 ` Wolfgang Denk
2009-05-29  0:36   ` Kim Phillips
2009-05-29  4:47     ` Stefan Roese
2009-05-29  8:29     ` Wolfgang Denk
2009-05-12  4:43 Stefan Roese
2009-05-15 19:06 ` Wolfgang Denk
2009-05-05 16:39 Stefan Roese
2009-05-10 19:59 ` Wolfgang Denk

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=4AFD6CB5.8080807@denx.de \
    --to=wg@denx.de \
    --cc=u-boot@lists.denx.de \
    /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