linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: firmware build failure
Date: Wed, 4 Jun 2008 20:40:50 +1000	[thread overview]
Message-ID: <20080604204050.6b60dc2a.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1212571377.4042.70.camel@shinybook.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]

Hi David,

On Wed, 04 Jun 2008 10:22:57 +0100 David Woodhouse <dwmw2@infradead.org> wrote:
>
> On Wed, 2008-06-04 at 16:46 +1000, Stephen Rothwell wrote:
> > -                 echo "    .align $(ASM_ALIGN)"                        >>$@;\
> > +                 echo "    .p2align $${ASM_ALIGN}"                     >>$@;\
> 
> Ah, thanks. I did originally start doing it with big C files with char
> arrays, which made this part easier -- but I really wanted to
> use .incbin so I didn't have to copy the whole of the object into
> 'source' code. Just checking that that actually does the right thing on
> ppc and ppc64 too, and I'll refactor it to include that. And the kaweth
> fix.

Great, thanks.

> Then I'll go seeking the usb tree of which you speak, with the ti patch
> that conflicts. This not the tree at
> kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6.git labelled 'junk
> tree; please ignore', I assume?

It is a quilt series here:
http://kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-04-usb/

All the trees and their sources are listed in the file Next/Trees in the
linux-next tree.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-06-04 10:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04  6:46 linux-next: firmware build failure Stephen Rothwell
2008-06-04  9:22 ` David Woodhouse
2008-06-04 10:40   ` Stephen Rothwell [this message]
2008-06-04  9:53 ` David Woodhouse
2008-06-04 10:47   ` Stephen Rothwell
2008-06-06  7:47 Stephen Rothwell
2008-06-06  9:09 ` David Woodhouse
2008-06-06  9:31 ` David Woodhouse
2008-06-12  6:28 Stephen Rothwell
2008-06-12  8:54 ` David Woodhouse

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=20080604204050.6b60dc2a.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dwmw2@infradead.org \
    --cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).