public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	hskinnemoen@atmel.com, cooloney@kernel.org, tony.luck@intel.com,
	ralf@linux-mips.org, dhowells@redhat.com, matthew@wil.cx,
	chris@zankel.net, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull -tip] headers_check fixes for other architectures
Date: Sun, 1 Feb 2009 11:39:36 +0100	[thread overview]
Message-ID: <20090201103936.GA30157@elte.hu> (raw)
In-Reply-To: <1233469811.5846.14.camel@localhost.localdomain>


* Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:

> On Sat, 2009-01-31 at 17:44 +0100, Ingo Molnar wrote:
> 
> > Then you can git-cherry-pick all your new commits into that new tree, and 
> > send a pull request if you are happy with it. Likewise, you can probably 
> > achieve the same (with a lot less work) by doing this in your master 
> > branch above:
> 
> The following changes since commit 7e3fa56141175026136b392fd026d5d07c49720e:
>   Sam Ravnborg (1):
>         kbuild: drop check for CONFIG_ in headers_check
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/jaswinder/linux-2.6-tip.git core/header-fixes
> 
> Jaswinder Singh Rajput (27):
>       headers_check fix: alpha, statfs.h
>       headers_check fix: alpha, swab.h
>       headers_check fix: arm, a.out.h
>       headers_check fix: arm, setup.h
>       headers_check fix: arm, swab.h
>       headers_check fix: avr32, swab.h
>       headers_check fix: blackfin, swab.h
>       headers_check fix: frv, swab.h
>       headers_check fix: h8300, swab.h
>       headers_check fix: ia64, fpu.h
>       headers_check fix: ia64, gcc_intrin.h
>       headers_check fix: ia64, intrinsics.h
>       headers_check fix: ia64, kvm.h
>       headers_check fix: ia64, swab.h
>       headers_check fix: m32r, swab.h
>       headers_check fix: mips, sigcontext.h
>       headers_check fix: mips, swab.h
>       headers_check fix: mn10300, swab.h
>       headers_check fix: parisc, pdc.h
>       headers_check fix: parisc, swab.h
>       headers_check fix: powerpc, bootx.h
>       headers_check fix: powerpc, elf.h
>       headers_check fix: powerpc, kvm.h
>       headers_check fix: powerpc, ps3fb.h
>       headers_check fix: powerpc, spu_info.h
>       headers_check fix: powerpc, swab.h
>       headers_check fix: xtensa, swab.h
> 
>  arch/alpha/include/asm/statfs.h     |    2 ++
>  arch/alpha/include/asm/swab.h       |    2 +-
>  arch/arm/include/asm/a.out.h        |    2 +-
>  arch/arm/include/asm/setup.h        |    2 +-
>  arch/arm/include/asm/swab.h         |    2 +-
>  arch/avr32/include/asm/swab.h       |    2 +-
>  arch/blackfin/include/asm/swab.h    |    2 +-
>  arch/h8300/include/asm/swab.h       |    2 +-
>  arch/ia64/include/asm/fpu.h         |    2 +-
>  arch/ia64/include/asm/gcc_intrin.h  |    1 +
>  arch/ia64/include/asm/intrinsics.h  |    1 +
>  arch/ia64/include/asm/kvm.h         |    3 +--
>  arch/ia64/include/asm/swab.h        |    2 +-
>  arch/mips/include/asm/sigcontext.h  |    1 +
>  arch/mips/include/asm/swab.h        |    2 +-
>  arch/parisc/include/asm/pdc.h       |    3 ++-
>  arch/parisc/include/asm/swab.h      |    2 +-
>  arch/powerpc/include/asm/bootx.h    |    2 +-
>  arch/powerpc/include/asm/elf.h      |    2 +-
>  arch/powerpc/include/asm/kvm.h      |    2 +-
>  arch/powerpc/include/asm/ps3fb.h    |    1 +
>  arch/powerpc/include/asm/spu_info.h |    3 ++-
>  arch/powerpc/include/asm/swab.h     |    2 +-
>  arch/xtensa/include/asm/swab.h      |    2 +-
>  include/asm-frv/swab.h              |    2 +-
>  include/asm-m32r/swab.h             |    2 +-
>  include/asm-mn10300/swab.h          |    2 +-
>  27 files changed, 30 insertions(+), 23 deletions(-)
> 
> These patches fixes 41 headers_check warnings as shown in first email.

Pulled into tip/core/header-fixes, thanks Jaswinder!

	Ingo

  reply	other threads:[~2009-02-01 10:40 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31  7:10 [git pull -tip] headers_check fixes for other architectures Jaswinder Singh Rajput
2009-01-31 16:44 ` Ingo Molnar
2009-02-01  6:30   ` Jaswinder Singh Rajput
2009-02-01 10:39     ` Ingo Molnar [this message]
2009-02-01 16:49       ` Ingo Molnar
2009-02-01 17:06         ` Russell King - ARM Linux
2009-02-01 17:20         ` Russell King - ARM Linux
2009-02-01 17:31           ` Jaswinder Singh Rajput
2009-02-01 18:33         ` Jaswinder Singh Rajput
2009-02-02 17:11         ` Mike Frysinger
2009-02-02 18:08           ` Ingo Molnar
2009-02-02 18:29             ` Mike Frysinger
2009-02-02 18:48               ` Ingo Molnar
2009-02-05 17:55 ` Tony Luck
2009-02-05 19:06   ` Linus Torvalds
2009-02-05 19:19     ` Ingo Molnar
2009-02-06  2:06       ` Jaswinder Singh Rajput
2009-02-06  2:14         ` Mike Frysinger
2009-02-06  2:20         ` Ingo Molnar
2009-02-06 14:18           ` Jaswinder Singh Rajput
2009-02-06 14:21             ` Russell King - ARM Linux
2009-02-06 14:34               ` Jaswinder Singh Rajput
2009-02-06 14:51                 ` Russell King - ARM Linux
2009-02-06 14:58                   ` Ingo Molnar
2009-02-06 15:00                   ` Jaswinder Singh Rajput
2009-02-06 15:10                     ` Russell King - ARM Linux
2009-02-06 15:56                       ` Ingo Molnar
2009-02-06 16:02                         ` Russell King - ARM Linux
2009-02-06 17:24             ` Sam Ravnborg
2009-02-06 17:40               ` Ingo Molnar
2009-02-06 18:11               ` Jaswinder Singh Rajput
2009-02-06 18:42                 ` Sam Ravnborg
2009-02-06 19:31                   ` Jaswinder Singh Rajput
2009-02-08  5:50               ` Jaswinder Singh Rajput
2009-02-09 12:23                 ` Ingo Molnar
2009-02-06  8:19 ` [linux-next][PATCH] revert headers_check fix: ia64, fpu.h KOSAKI Motohiro
2009-02-06  8:53   ` Jaswinder Singh Rajput
2009-02-06  9:11     ` KOSAKI Motohiro
2009-02-06 14:55       ` Ingo Molnar
2009-02-06 15:29         ` Jaswinder Singh Rajput
2009-02-06 15:33           ` Russell King - ARM Linux
2009-02-06 15:45             ` Ingo Molnar
2009-02-06 15:49               ` Russell King - ARM Linux
2009-02-06 16:01                 ` Ingo Molnar
2009-02-06 15:48             ` Jaswinder Singh Rajput
2009-02-06 15:55               ` Russell King - ARM Linux
2009-02-06 16:12                 ` Ingo Molnar
2009-02-06 16:23                   ` Russell King - ARM Linux
2009-02-06 16:33                     ` Ingo Molnar
2009-02-06 16:38                       ` Russell King - ARM Linux
2009-02-06 17:14                         ` Ingo Molnar
2009-02-06 17:22                           ` Russell King - ARM Linux
2009-02-06 17:32                 ` Sam Ravnborg
2009-02-06 17:41                   ` Ingo Molnar
2009-02-06 18:53     ` Luck, Tony
2009-02-06 13:42   ` 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=20090201103936.GA30157@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=chris@zankel.net \
    --cc=cooloney@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=hskinnemoen@atmel.com \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=matthew@wil.cx \
    --cc=ralf@linux-mips.org \
    --cc=sam@ravnborg.org \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.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