linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Subject: Re: linux-next: manual merge of the ubifs tree
Date: Thu, 24 Jul 2008 12:01:20 +0300	[thread overview]
Message-ID: <488844E0.10403@nokia.com> (raw)
In-Reply-To: <20080724085945.GA32109@cs181140183.pp.htv.fi>

Adrian Bunk wrote:
> On Thu, Jul 24, 2008 at 10:42:20AM +0300, Artem Bityutskiy wrote:
>> Stephen Rothwell wrote:
>>> Today's linux-next merge of the ubifs tree got conflicts in
>>> Documentation/filesystems/ubifs.txt, fs/ubifs/budget.c,
>>> fs/ubifs/commit.c, fs/ubifs/debug.c, fs/ubifs/dir.c, fs/ubifs/file.c,
>>> fs/ubifs/io.c, fs/ubifs/journal.c, fs/ubifs/log.c, fs/ubifs/misc.h,
>>> fs/ubifs/orphan.c, fs/ubifs/super.c and fs/ubifs/ubifs.h against Linus'
>>> tree.
>>>
>>> This has happened because of a partial merge of this tree into Linus'
>>> tree.  I just took the ubifs tree's version of all those files.
>> Oh. This is because I still have my tree based on 2.6.26, + the same
>> patches which are in Linus's tree, + more. I thought you scrips would
>> somehow magically deal with this.
>>
>> I was reluctant to switch to linus tree because the tg3 driver does
>> not compile. I will try again, sorry for these troubles.
> 
> Are you referring to the firmware compile glitch (that was fixed Monday 
> last week) or what compile error do you get?

Not entirely sure. Anyway, it compiles fine now. I'll fix my trees.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2008-07-24  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24  5:22 linux-next: manual merge of the ubifs tree Stephen Rothwell
2008-07-24  7:42 ` Artem Bityutskiy
2008-07-24  8:59   ` Adrian Bunk
2008-07-24  9:01     ` Artem Bityutskiy [this message]
2008-07-24  9:15 ` Artem Bityutskiy
  -- strict thread matches above, loose matches on Subject: below --
2008-07-17  7:10 Stephen Rothwell
2008-07-17  7:23 ` Artem Bityutskiy

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=488844E0.10403@nokia.com \
    --to=artem.bityutskiy@nokia.com \
    --cc=bunk@kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).