public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Ingo Molnar <mingo@elte.hu>, Sam Ravnborg <sam@ravnborg.org>,
	x86 maintainers <x86@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	David Howells <dhowells@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git-pull -tip] headers_check fix patches 20090610
Date: Thu, 11 Jun 2009 11:35:56 +1000	[thread overview]
Message-ID: <4A305F7C.9000308@snapgear.com> (raw)
In-Reply-To: <1244647176.3070.8.camel@ht.satnam>

Hi Jaswinder,

Jaswinder Singh Rajput wrote:
> Hello Stephen,
> 
> On Thu, 2009-06-11 at 00:19 +1000, Stephen Rothwell wrote:
>> Hi Jaswinder,
>>
>> On Wed, 10 Jun 2009 19:00:30 +0530 Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
>>> The following changes since commit e271e1343a94e081723cb4180af3fdb5fecc1a49:
>>>   Ingo Molnar (1):
>>>         Merge branch 'x86/mce4'
>>>
>>> are available in the git repository at:
>>>
>>>   git://git.kernel.org/pub/scm/linux/kernel/git/jaswinder/linux-2.6-top.git master
>>>
>>> Jaswinder Singh Rajput (3):
>>>       headers_check fix: m68k, swab.h
>>>       headers_check fix: mn10300, ptrace.h
>>>       headers_check fix: mn10300, setup.h
>>>
>>>  arch/m68k/include/asm/swab.h      |    2 +-
>>>  arch/mn10300/include/asm/ptrace.h |    5 ++---
>>>  arch/mn10300/include/asm/setup.h  |    3 ++-
>>>  3 files changed, 5 insertions(+), 5 deletions(-)
>> Is there some reason that these fixes are not just sent to the appropriate
>> maintainers?  That way we would avoid unnecessary conflicts cropping up.
>>
> 
> Maintainers are also in CC.
> Patches were already sent on :
> 
> Subject: [PATCH 0/6] headers_check fix patches 20090604
> 
> Interested maintainers already pulled and applied patches. These are
> left-over patches. I am sending to Ingo hoping that he will merge it
> otherwise last option for me will be to prepare headers-check tree and
> send to linux-next ;-)

I am happy to take the m68k change and push that upstream.
If it hasn't already been picked up by someone else.

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

  reply	other threads:[~2009-06-11  1:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 13:30 [git-pull -tip] headers_check fix patches 20090610 Jaswinder Singh Rajput
2009-06-10 14:19 ` Stephen Rothwell
2009-06-10 15:17   ` Ingo Molnar
2009-06-10 15:19   ` Jaswinder Singh Rajput
2009-06-11  1:35     ` Greg Ungerer [this message]
2009-06-11 10:26       ` Jaswinder Singh Rajput
2009-06-11 10:52         ` Greg Ungerer

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=4A305F7C.9000308@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=sfr@canb.auug.org.au \
    --cc=x86@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