From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Conflicting commits for seaboard USB keyboard handling
Date: Sat, 15 Dec 2012 17:41:08 +0100 [thread overview]
Message-ID: <20121215174108.7d2cd36f@lilith> (raw)
In-Reply-To: <20121211190209.GB25496@badger>
Hi Allen,
On Tue, 11 Dec 2012 11:02:09 -0800, Allen Martin <amartin@nvidia.com>
wrote:
> On Mon, Dec 10, 2012 at 01:51:40PM -0800, Tom Warren wrote:
> > Albert,
> >
> > > On Sat, Dec 8, 2012 at 11:03 PM, Albert ARIBAUD
> > > <albert.u.boot@aribaud.net> wrote:
> > >> Hello,
> > >>
> > >> It seems like two commits 5ddcc38b (in u-boot, committed by Marek)
> > >> 29f3e3f2 (in u-boot-arm, committed by Tom from u-boot-tegra) are
> > >> conflicting on the seaboard configuration header file for USB (and
> > >> possibly other areas).
> >
> > One possible problem is that I've got new commits ready in
> > u-boot-tegra/next that were almost ready for a pull request, so I
> > copied them over to my tegra/master branch and pushed to
> > u-boot-tegra/master on denx. I assumed that once I got the 'applied
> > to u-boot-arm/master' response from you, that I could stage the next
> > pull request. But if you (or Allen) are pulling from
> > u-boot-tegra/master )or /next), you're gonna get commits that haven't
> > been merged into u-boot-arm/master.
> >
> > I can push the older tegra/master branch back to denx.de (the one that
> > I requested a pull from on Nov 19th) if that'll help. But I'm not
> > sure how it would help, since all those commits should have been
> > present in u-boot-arm/master (from my pull request) when you went to
> > merge w/u-boot/master.
> >
> > So I'm still not seeing how the conflict arose, or what the path is to
> > fixing it.
> >
>
> The conflict came from my config file changes for tegra USB keyboard
> which went up to u-boot/master through Marek's tree becasue they
> depend on my USB DMA alignment fix which was not a tegra change.
> There are subsequent changes in both the tegra and arm trees that were
> not based on that change, so they now conflict when attempting to
> merge back into u-boot/master.
>
> It's trivial for me to resolve the conflict since I have context on
> the changes. I see that there are other merge conflicts between
> u-boot/master and u-boot-arm/master though, so I'm not sure how to
> proceed. Albert do you just want me to post merged versions of the
> two files that conflict, so you know how to resolve the conflict
> during your merge?
I would like you to post a pull request that would fix the two file
conflicts; I have asked other people to fix other merge conflicts. I
will merge all fix branches in one go (so that u-boot-arm keeps
building clean) once all fix branches are available.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2012-12-15 16:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 6:03 [U-Boot] Conflicting commits for seaboard USB keyboard handling Albert ARIBAUD
2012-12-10 16:25 ` Tom Warren
2012-12-10 16:59 ` Tom Warren
2012-12-10 19:25 ` Allen Martin
2012-12-10 21:15 ` Tom Warren
2012-12-10 21:51 ` Tom Warren
2012-12-11 19:02 ` Allen Martin
2012-12-15 16:41 ` Albert ARIBAUD [this message]
2012-12-17 22:13 ` Tom Warren
2012-12-17 22:22 ` Allen Martin
2012-12-18 16:43 ` Tom Warren
2012-12-18 18:06 ` Allen Martin
2012-12-18 23:59 ` Tom Warren
2012-12-19 1:08 ` Allen Martin
2012-12-19 6:04 ` Stephen Warren
2012-12-19 19:37 ` Albert ARIBAUD
2012-12-19 21:11 ` Allen Martin
2012-12-19 22:42 ` Albert ARIBAUD
2012-12-20 0:32 ` Allen Martin
2012-12-20 17:16 ` Tom Warren
2012-12-13 19:20 ` Albert ARIBAUD
2012-12-14 16:48 ` Tom Warren
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=20121215174108.7d2cd36f@lilith \
--to=albert.u.boot@aribaud.net \
--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