From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ignore soc asm-offsets.s
Date: Thu, 29 Sep 2011 10:30:10 -0400 [thread overview]
Message-ID: <201109291030.14210.vapier@gentoo.org> (raw)
In-Reply-To: <20110929124033.GG10893@guralp.com>
On Thursday, September 29, 2011 08:40:33 Laurence Withers wrote:
> On Mon, Sep 12, 2011 at 12:47:24AM -0400, Mike Frysinger wrote:
> > Recent commit a4814a69d3bca6ee05f4bfc4 cleaned up generation of
> > asm-offsets.s for SoC dirs, but missed adding it to the ignore
> > list which makes it show up in `git status`.
> >
> > --- a/.gitignore
> > +++ b/.gitignore
> >
> > /lib/asm-offsets.s
> > +/arch/*/cpu/asm-offsets.s
>
> There appear to be some SoCs which have further subdirectories, e.g.:
>
> lwithers at rhodium u-boot $ git status
> # On branch lw-diamond
> # Untracked files:
> # (use "git add <file>..." to include in what will be committed)
> #
> # arch/arm/cpu/arm926ejs/davinci/asm-offsets.s
> nothing added to commit but untracked files present (use "git add" to
> track)
>
> We could ignore all files named asm-offsets.s , or perhaps all files under
> arch ?
off the top of my head, i can't see a problem with ignoring asm-offsets.s in
the whole tree. want to send a patch and see what Wolfgang says ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110929/c6bde4ed/attachment.pgp
prev parent reply other threads:[~2011-09-29 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 4:47 [U-Boot] [PATCH] ignore soc asm-offsets.s Mike Frysinger
2011-09-21 21:02 ` Wolfgang Denk
2011-09-29 12:40 ` Laurence Withers
2011-09-29 14:30 ` Mike Frysinger [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=201109291030.14210.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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