From: Martin Michlmayr <tbm@cyrius.com>
To: Andrew Morton <akpm@osdl.org>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: Bring linux-mips in sync with Linus' tree
Date: Mon, 20 Mar 2006 05:20:27 +0000 [thread overview]
Message-ID: <20060320052027.GE16906@deprecation.cyrius.com> (raw)
In-Reply-To: <20060319210617.744338e1.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> [2006-03-19 21:06]:
> > The following is a series of six patches to bring the linux-mips tree
> > in sync with Linus' tree. These are changes that have to be made
> > on the linux-mips side.
> Confused. Isn't all this stuff in Ralf's git tree? It should be.
I CCed you on this series not because you have to do anything about
it, but just as a reference since I mentioned this series in the
series that is for you (the 12 patches, for which I put you in the To:
line).
The point is that these six patches are missing from Ralf's tree, even
though they're in mainline, or that random changes were made in Ralf's
tree that no longer apply and should be reverted.
> That way, it all gets merged when Ralf does his next Linus merge.
Well, in theory, yes. In practice, they have always fallen through
the cracks so far when Ralf did a merge... or, rather, most of these
changes are changes that were made on the linux-mips at same time but
need to be reverted because they no longer apply.
I'm not sure I'm expressing myself very clear, so please ask if none
of this makes sense.
Okay, let me summarize:
[PATCH 1/6] [CHAR] Remove obsolete IBM z50 (vr41xx) keyboard map
-> got applied to linux-mips, never made it into mainline. There's
no keyboard support anyway, so this should just be removed.
[PATCH 2/6] [VIDEO] Remove trailing whitespace from drivers/video/Kconfig
-> I suppose the trailing whitespace got dropped when those patches
made it into mainline, but for some reason the whitespace changes
never got merged back into linux-mips when Ralf synced.
[PATCH 3/6] Remove bogus blank lines - sync with Linus' tree
-> These were introduced while doctoring around some bogus changes
instead of pulling from mainline.
[PATCH 4/6] [NET] Fix NET_SB1250_MAC Kconfig order to match Linus' tree
-> no idea why we differ here, but we shouldn't.
[PATCH 5/6] [MIPS] vr41xx: remove timex.h
-> mips-linux specific addition that no longer applies
[PATCH 6/6] [MTD] Remove typecast from drivers/mtd/maps/lasat.c
-> no idea why this never got synced from mainline
Clearer now?
--
Martin Michlmayr
http://www.cyrius.com/
prev parent reply other threads:[~2006-03-20 5:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 4:34 Bring linux-mips in sync with Linus' tree Martin Michlmayr
2006-03-20 4:35 ` [PATCH 1/6] [CHAR] Remove obsolete IBM z50 (vr41xx) keyboard map Martin Michlmayr
2006-03-20 4:35 ` [PATCH 2/6] [VIDEO] Remove trailing whitespace from drivers/video/Kconfig Martin Michlmayr
2006-03-20 4:35 ` [PATCH 3/6] Remove bogus blank lines - sync with Linus' tree Martin Michlmayr
2006-03-20 4:36 ` [PATCH 4/6] [NET] Fix NET_SB1250_MAC Kconfig order to match " Martin Michlmayr
2006-03-20 4:36 ` [PATCH 5/6] [MIPS] vr41xx: remove timex.h Martin Michlmayr
2006-03-20 4:36 ` [PATCH 6/6] [MTD] Remove typecast from drivers/mtd/maps/lasat.c Martin Michlmayr
2006-03-20 5:06 ` Bring linux-mips in sync with Linus' tree Andrew Morton
2006-03-20 5:20 ` Martin Michlmayr [this message]
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=20060320052027.GE16906@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=akpm@osdl.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/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