All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Sieka <tur@semihalf.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Marian Balakowicz <m8@semihalf.com>
Subject: Re: Please pull linux-2.6-mpc52xx.git
Date: Tue, 18 Mar 2008 08:57:25 +0100	[thread overview]
Message-ID: <47DF75E5.9000800@semihalf.com> (raw)
In-Reply-To: <fa686aa40803171219s7135a0f8n91bcd20329a94637@mail.gmail.com>

Grant Likely wrote:
> On Mon, Mar 17, 2008 at 9:57 AM, Bartlomiej Sieka <tur@semihalf.com> wrote:
[...]
>>  we were hoping that the changes would go upstream (in 2.6.25). I can see
>>  that the .dts files for those boards are in the mainline already, but I
>>  see no trace of for example _defconfig files -- could you shed some
>>  light on this?
> 
> Yes, the separate dts files have been dropped in preference for a
> single mpc5200_defconfig for all 5200 boards.

Ah, yes. I was searching for patches by Marian, and missed the defconfig
unification patch by you. BTW: I can't find it using its description 
from the commit log (i.e., "[POWERPC] mpc5200: merge defconfigs for all 
mpc5200 boards") in Nabble's archive of linuxppc ML; searching 
patchwork.ozlabs.org/linuxppc fails as well. Should I search
using some other description?

Regards,
Bartlomiej

  parent reply	other threads:[~2008-03-18  8:30 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24  7:35 Please pull linux-2.6-mpc52xx.git Grant Likely
     [not found] ` <47DE94F4.90804@semihalf.com>
2008-03-17 19:19   ` Grant Likely
2008-03-17 20:59     ` Wolfgang Denk
2008-03-17 21:43       ` Grant Likely
2008-03-17 22:28         ` Wolfgang Denk
2008-03-17 23:43           ` Grant Likely
2008-03-18  0:26             ` Wolfgang Denk
2008-03-18  2:42               ` Grant Likely
2008-03-18 12:20                 ` Josh Boyer
2008-03-18  8:29             ` Bartlomiej Sieka
2008-03-18 10:04               ` Richard Purdie
2008-03-25 15:29                 ` Bartlomiej Sieka
2008-03-18 14:47               ` Grant Likely
2008-03-18 16:41                 ` Richard Purdie
2008-03-18 16:53                   ` Grant Likely
2008-03-25 16:50                     ` Bartlomiej Sieka
2008-03-25 18:49                       ` Grant Likely
2008-03-25 17:38             ` Bartlomiej Sieka
2008-03-25 18:51               ` Grant Likely
2008-04-01 12:37                 ` Bartlomiej Sieka
2008-04-04 11:13                   ` Bartlomiej Sieka
2008-04-04 16:11                     ` Grant Likely
2008-04-04 16:14                       ` Grant Likely
2008-04-04 16:38                         ` Olof Johansson
2008-04-04 17:15                           ` Josh Boyer
2008-04-04 17:25                             ` Grant Likely
2008-04-15 10:34                       ` Bartlomiej Sieka
2008-03-18  7:57     ` Bartlomiej Sieka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-09 23:09 Grant Likely
2008-11-14 19:20 Grant Likely
2008-11-24  3:38 ` Paul Mackerras
2008-11-24 14:41   ` Grant Likely
2008-05-01 18:04 Grant Likely
2008-04-29 13:34 Grant Likely
2007-10-16 23:22 Grant Likely
2007-10-17 10:27 ` Paul Mackerras
2007-10-17 13:13   ` Grant Likely
2007-10-10 16:30 Grant Likely
2007-10-11 17:35 ` tnt

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=47DF75E5.9000800@semihalf.com \
    --to=tur@semihalf.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=m8@semihalf.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.