From: Jon Loeliger <jdl@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [Patch 1/3] U-Boot-V2: Bitops cleanup: introduce asm-generic bitops
Date: Thu, 19 Jun 2008 07:56:38 -0500 [thread overview]
Message-ID: <485A5786.8020105@freescale.com> (raw)
In-Reply-To: <7A436F7769CA33409C6B44B358BFFF0CD3211907@dlee02.ent.ti.com>
Menon, Nishanth wrote:
> Sascha,
> The following 3 patches are for cleaning up the bitops
>> -----Original Message-----
>> From: Sascha Hauer [mailto:s.hauer at pengutronix.de]
>> Sent: Wednesday, June 18, 2008 10:51 AM
>> To: Menon, Nishanth
>> Cc: Kamat, Nishant; u-boot-users at lists.sourceforge.net; Laurent Desnogues; philip.balister at gmail.com;
>> dirk.behme at googlemail.com
>> Subject: Re: [Patch 2/9] U-boot-V2:ARM: Introduce additional bitops
>>
>>
>> In the kernel are generic bitops, #ifdefed with CONFIG_GENERIC_XXX
Again, either leave the above crap out entirely or place it
below the triple-dash line.
> This introduces selected generic bitop files from kernel. We don't need minix, ext2, sched or lock based bitops. Those have been dropped.
Line wrap the log message at 70 or 72.
> Signed-off-by: Nishanth Menon <x0nishan@ti.com>
>
> ---
> include/asm-generic/bitops/__ffs.h | 43 ++++++++++++++++
> include/asm-generic/bitops/__fls.h | 43 ++++++++++++++++
Thanks,
jdl
next prev parent reply other threads:[~2008-06-19 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 12:34 [U-Boot-Users] [Patch 2/9] U-boot-V2:ARM: Introduce additional bitops Menon, Nishanth
2008-06-18 15:30 ` Sascha Hauer
2008-06-18 15:41 ` Menon, Nishanth
2008-06-18 15:50 ` Sascha Hauer
2008-06-19 6:12 ` [U-Boot-Users] [Patch 1/3] U-Boot-V2: Bitops cleanup: introduce asm-generic bitops Menon, Nishanth
2008-06-19 12:56 ` Jon Loeliger [this message]
2008-06-19 6:13 ` [U-Boot-Users] [Patch 2/3] U-Boot-V2: Bitops cleanup: cleanup ARM bitops Menon, Nishanth
2008-06-19 6:13 ` [U-Boot-Users] [Patch 3/3] U-Boot-V2: Bitops cleanup: cleanup rest of generic_xxx functions Menon, Nishanth
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=485A5786.8020105@freescale.com \
--to=jdl@freescale.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