From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Mike Frysinger" <vapier@gentoo.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] make hdrscheck.sh force __asm__ in exported headers
Date: Mon, 18 Jun 2007 02:28:10 -0400 [thread overview]
Message-ID: <8bd0f97a0706172328y1e433ea7gc5c10080f8950770@mail.gmail.com> (raw)
In-Reply-To: <20070617223436.2125b1a4.akpm@linux-foundation.org>
On 6/18/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Mon, 18 Jun 2007 01:17:46 -0400 Mike Frysinger <vapier@gentoo.org> wrote:
> > On Monday 18 June 2007, Andrew Morton wrote:
> > > And does the kernel pass these checks?
> >
> > nope ... should i audit the arches before this gets merged ?
>
> Yes please. I'd rather not break things in this fashion: it causes a storm
> of emails which I need to redirect to the appropriate maintainers who then
> take an arbitrarily long time to do anything. Meanwhile lots of testers
> get impacted and this reduces the testing level of all the other thousands
> of patches in there.
with the few patches i just sent out, the following pass:
alpha arm avr32 blackfin i386 ia64 m68k mips powerpc s390 sh sparc x86_64
cris and parisc fail vanilla git regardless
-mike
next prev parent reply other threads:[~2007-06-18 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 22:54 Mike Frysinger
2007-06-18 5:11 ` Andrew Morton
2007-06-18 5:17 ` Mike Frysinger
2007-06-18 5:34 ` Andrew Morton
2007-06-18 5:53 ` Mike Frysinger
2007-06-18 5:54 ` Mike Frysinger
2007-06-18 6:28 ` Mike Frysinger [this message]
2007-06-18 7:54 ` Sam Ravnborg
2007-06-18 8:07 ` Mike Frysinger
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=8bd0f97a0706172328y1e433ea7gc5c10080f8950770@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier@gentoo.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
all inboxes | Powered by JetHome®