Re: [PATCH] scripts/checksyscalls.sh: only whine perf_counter_openwhen supported

From: Ingo Molnar
Date: Fri Jun 12 2009 - 11:57:02 EST



* Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:

> > > On Fri, Jun 12, 2009 at 09:09, Ingo Molnar wrote:
> > > > * Mike Frysinger <vapier.adi@xxxxxxxxx> wrote:
> > > >> On Fri, Jun 12, 2009 at 08:59, Ingo Molnar wrote:
> > > >> > * Mike Frysinger <vapier.adi@xxxxxxxxx> wrote:
> > > >> >> On Fri, Jun 12, 2009 at 08:31, Ingo Molnar wrote:
> > > >> >> > * Mike Frysinger <vapier.adi@xxxxxxxxx> wrote:
> > > >> >> >> On Fri, Jun 12, 2009 at 08:17, Ingo Molnar wrote:
> > > >> >> >> > * Mike Frysinger <vapier.adi@xxxxxxxxx> wrote:
> > > >> >> >> >> On Fri, Jun 12, 2009 at 08:05, Ingo Molnar wrote:
> > > >> >> >> >> > * Mike Frysinger <vapier@xxxxxxxxxx> wrote:
> >
>
> > Anyway, i have no time to teach you about kernel mainteinance basics
> > really so i probably wont follow up on future emails.
>
> So yet again you resort to personal attacks when someone objects to the
> world according to Ingo. [...]

You snipped out the proper context. The thing i object to above was
a technically completely unacceptable solution proposed by Mike:

| #ifndef __NR_perf_counter_open
| # error sorry, your arch has not hooked up perf_counter_open syscall yet
| #endif
|
| is completely unacceptable. We dont propagate build failures via
| user-enable config options, we never did. There's a lot of people
| doing randconfig builds - if it randomly failed due to your 'fix'
| that would upset a lot of testing for no good reason.

and that opinion still holds. (If you disagree then go try to push
such a solution upstream, and please share with me the various
replies you will get, it will be an entertaining read.)

Mike made valid technical points later on though and i replied to
them and accepted most of them. We can certainly annotate out that
warning message from scripts/checksyscalls.sh.

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/