From: David Laight <David.Laight@ACULAB.COM>
To: 'Linus Torvalds' <torvalds@linux-foundation.org>
Cc: Mateusz Guzik <mjguzik@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
"Uros Bizjak" <ubizjak@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] lib/genalloc: use try_cmpxchg in {set,clear}_bits_ll
Date: Tue, 24 Jan 2023 17:32:57 +0000 [thread overview]
Message-ID: <1d272a31a0494c4b8b1b86d1a79f1b96@AcuMS.aculab.com> (raw)
In-Reply-To: <CAHk-=wiqpD6F0ript8y29X_ijwsBmK_ZDVy_bOBMPr2zb09B5A@mail.gmail.com>
> (Obviously it's still faster to not have to even search at all, and
> put everything in one directory and not have a search path at all, but
> it does have its own serious downsides, notably the whole "now we have
> to keep that union directory in sync with all the source directories")
I've used make to do the copies for a 'day job' project.
Just a matter of identifying the .h files that need copying
to obj/include.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2023-01-24 17:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 15:07 Uros Bizjak
2023-01-18 21:18 ` Andrew Morton
2023-01-18 21:47 ` Uros Bizjak
2023-01-18 21:55 ` Uros Bizjak
2023-01-18 22:01 ` Uros Bizjak
2023-01-19 12:47 ` David Laight
2023-01-23 15:04 ` Uros Bizjak
2023-01-23 15:42 ` David Laight
2023-01-23 15:59 ` Mateusz Guzik
2023-01-23 19:36 ` Linus Torvalds
2023-01-24 0:11 ` Mateusz Guzik
2023-01-24 1:51 ` Linus Torvalds
2023-01-24 6:48 ` Mateusz Guzik
2023-01-24 8:54 ` David Laight
2023-01-24 16:58 ` Linus Torvalds
2023-01-24 17:32 ` David Laight [this message]
2023-01-27 3:54 ` Al Viro
2023-01-27 19:25 ` Linus Torvalds
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=1d272a31a0494c4b8b1b86d1a79f1b96@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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®