From: Sebastien Carlier <sebastien.carlier@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Switch from library archives to partial linking
Date: Sun, 07 Nov 2010 16:11:14 +0100 [thread overview]
Message-ID: <4CD6C192.20008@gmail.com> (raw)
In-Reply-To: <1289139379.13696.12.camel@ptyser-laptop>
Dear Peter,
On 11/07/2010 03:16 PM, Peter Tyser wrote:
> You shouldn't need to send the patch using "git send-email". The patch
> is greater than U-Boot's mailing list limit (100k) and posting the patch
> on a website is perfectly acceptable. Also, it shouldn't be necessary
> to split the patch into each separate patch's to address each lib. It'd
> be a lot of work on Sebastien's part to do this and not break bisection,
> and most maintainers can either ack this patch, or probably don't need
> to since its more of a build change, not low-level change that a
> maintainer has insight into.
>
That makes a lot of sense.
> I had a couple of comments though:
> - You need to add your "Signed-of-by: " line to the patch.
>
Okay. As you may have guessed, I am a first-time git user.
> - A patch description illustrating why this approach is better than the
> current approach would be appreciated.
>
Will do.
> - You shouldn't be making changes to stuff like CONFIG_CMD_NFS in this
> patch. Its unrelated, and should be dealt with in another patch. eg
> your patches could be:
> 1/2: Fix boards with CONFIG_CMD_NFS but !CONFIG_CMD_NET
> 2/2: Switch from library archives to partial linking
>
Sounds good, will do.
> I'm guessing lots of boards will have this same issue. I imagine its
> due to include/config_cmd_defaults.h, so maybe if you fix the issue in
> that one place all the compile issues will go away.
>
The generic fix is to include the following lines somewhere at the end
of the config.h generated in the mkconfig script:
#ifndef CONFIG_CMD_NET
# undef CONFIG_CMD_NFS
#endif
These lines should probable be put in a new header file; would
config_checks.h be an ok name for it? I suppose there might be other
cases where a module (that is included by default) needs to be excluded
when one of its dependencies is disabled.
Regards,
Sebastien Carlier
next prev parent reply other threads:[~2010-11-07 15:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 10:39 [U-Boot] Weak symbols: request for comments Sebastien Carlier
2010-11-05 11:01 ` Andre Schwarz
2010-11-05 11:16 ` Reinhard Meyer
2010-11-05 12:16 ` Sebastien Carlier
2010-11-05 12:23 ` Wolfgang Denk
2010-11-05 12:57 ` Sebastien Carlier
2010-11-06 14:28 ` [U-Boot] [PATCH] Switch from library archives to partial linking Sebastien Carlier
2010-11-06 17:21 ` Albert ARIBAUD
2010-11-07 14:16 ` Peter Tyser
2010-11-07 15:11 ` Sebastien Carlier [this message]
2010-11-07 15:30 ` Andreas Bießmann
2010-11-07 16:18 ` Sebastien Carlier
2010-11-07 16:54 ` Andreas Bießmann
2010-11-10 4:41 ` Mike Frysinger
2010-11-07 21:46 ` Wolfgang Denk
2010-11-07 22:24 ` Peter Tyser
2010-11-07 22:33 ` Wolfgang Denk
2010-11-05 12:30 ` [U-Boot] Weak symbols: request for comments Reinhard Meyer
2010-11-05 11:21 ` Andreas Bießmann
2010-11-05 12:04 ` Joakim Tjernlund
2010-11-05 12:14 ` Wolfgang Denk
2010-11-05 12:40 ` Sebastien Carlier
2010-11-05 15:00 ` Sebastien Carlier
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=4CD6C192.20008@gmail.com \
--to=sebastien.carlier@gmail.com \
--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