From: Geert Uytterhoeven <geert@linux-m68k.org>
To: arnd@arndb.de
Cc: linux-arch@vger.kernel.org
Subject: Re:
Date: Mon, 27 Apr 2009 16:50:50 +0200 [thread overview]
Message-ID: <10f740e80904270750n6f9bb593r8c2b6a257b034cea@mail.gmail.com> (raw)
In-Reply-To: <20090427143737.584097988@arndb.de>
[bummer, reply-to-all broken]
On Mon, Apr 27, 2009 at 16:41, <arnd@arndb.de> wrote:
> Subject: [RFC 06/17] asm-generic: add a complete signal.h
> There used to be an asm-generic/signal.h, but not one that
> could be used out of the box. This renames the existing file
> to asm-generic/signal-defs.h and adds a new asm-generic/signal.h
The rename was done in another patch, but you forgot to update this
patch description?
> with common definitions for sigaction and sigaltstack, but
> not for the old-style signal handlers.
>
> New architectures should only implement rt-signals and use this
> generic header.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Remis Lima Baima <remis.developer@googlemail.com>
> ---
> ---
> include/asm-generic/Kbuild | 1 1 + 0 - 0 !
> include/asm-generic/signal.h | 131 131 + 0 - 0 !
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2009-04-27 14:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 14:41 arnd
2009-04-27 14:50 ` Geert Uytterhoeven [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-02 1:10 [PATCH] lib/find_bit: Add find_prev_*_bit functions Yun Levi
2020-12-02 9:47 ` Andy Shevchenko
2020-12-02 10:04 ` Rasmus Villemoes
2020-12-02 11:50 ` Yun Levi
[not found] ` <CAAH8bW-jUeFVU-0OrJzK-MuGgKJgZv38RZugEQzFRJHSXFRRDA@mail.gmail.com>
2020-12-02 18:22 ` Yun Levi
2020-12-02 21:26 ` Yury Norov
2020-12-02 22:51 ` Yun Levi
2020-12-03 1:23 ` Yun Levi
2020-12-03 8:33 ` Rasmus Villemoes
2020-12-03 9:47 ` Re: Yun Levi
2020-12-03 18:46 ` Re: Yury Norov
2020-12-03 18:52 ` Re: Willy Tarreau
2020-12-04 1:36 ` Re: Yun Levi
2020-12-04 18:14 ` Re: Yury Norov
2020-12-05 0:45 ` Re: Yun Levi
2020-12-05 11:10 ` Re: Rasmus Villemoes
2020-12-05 18:20 ` Re: Yury Norov
2018-01-24 19:54 Re: Amy Riddering
2017-11-13 14:55 Re: Amos Kalonzo
2017-02-23 15:09 Qin's Yanjun
2015-08-19 13:01 christain147
2014-12-01 13:02 Re: Quan Han
2012-10-06 23:15 (unknown), David Howells
2012-10-07 6:36 ` Geert Uytterhoeven
2012-10-11 9:57 ` Re: Will Deacon
2012-05-20 22:20 Re: Mr. Peter Wong
2011-05-23 9:11 Re: Young Chang
2010-02-25 12:08 chau chin
2009-04-27 14:42 arnd
2009-04-27 23:52 ` Greg Ungerer
2007-08-14 23:04 [PATCH 0/24] make atomic_read() behave consistently across all architectures Chris Snook
2007-08-15 6:49 ` Herbert Xu
2007-08-15 8:18 ` Heiko Carstens
2007-08-15 13:53 ` Stefan Richter
2007-08-15 14:35 ` Satyam Sharma
2007-08-15 14:52 ` Herbert Xu
2007-08-15 16:09 ` Stefan Richter
2007-08-15 16:27 ` Paul E. McKenney
2007-08-15 18:31 ` Segher Boessenkool
2007-08-15 18:57 ` Paul E. McKenney
2007-08-15 19:54 ` Satyam Sharma
2007-08-15 20:47 ` Segher Boessenkool
2007-08-16 0:36 ` Satyam Sharma
2007-08-16 1:38 ` Segher Boessenkool
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=10f740e80904270750n6f9bb593r8c2b6a257b034cea@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).