mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Riley Williams" <Riley@Williams.Name>
To: "Sam Ravnborg" <sam@ravnborg.org>,
	"Linus Torvalds" <torvalds@transmeta.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] kbuild: Document lib-y
Date: Tue, 17 Jun 2003 23:16:15 +0100	[thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAEEOBEFAA.Riley@Williams.Name> (raw)
In-Reply-To: <20030608180113.GA3987@mars.ravnborg.org>

Hi Sam.

 > Hi Linus, documentation for the newly added lib-y.

Minor grammatical tweaks to the same...

 > ===== Documentation/kbuild/makefiles.txt 1.8 vs edited =====
 > --- 1.8/Documentation/kbuild/makefiles.txt	Sun Mar 16 06:52:28 2003
 > +++ edited/Documentation/kbuild/makefiles.txt	Sun Jun  8 
 > @@ -214,20 +214,33 @@
 >  	modules exporting symbols.
 >  	See also Documentation/modules.txt.
 >  
 > ---- 3.5 Library file goals - L_TARGET
 > +--- 3.5 Library file goals - lib-y
 >  
 > -	Instead of building a built-in.o file, you may also
 > -	build an archive which again contains objects listed in $(obj-y).
 > -	This is normally not necessary and only used in lib/ and 
 > -	arch/$(ARCH)/lib directories.
 > -	Only the name lib.a is allowed.
 > +	Objects listed with obj-* is used for modules or
                                ^^
That should be "are" ?

 > +	are combined in a built-in.o for that specific directory.
      ^^^
That shouldn't be there.

Best wishes from Riley.
---
 * Nothing as pretty as a smile, nothing as ugly as a frown.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.490 / Virus Database: 289 - Release Date: 16-Jun-2003


  reply	other threads:[~2003-06-17 22:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08 18:01 Sam Ravnborg
2003-06-17 22:16 ` Riley Williams [this message]
2003-06-21  6:21   ` Sam Ravnborg

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=BKEGKPICNAKILKJKMHCAEEOBEFAA.Riley@Williams.Name \
    --to=riley@williams.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®