All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: nick <xerofoify@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	dave.hansen@linux.intel.com, bp@suse.de, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Obsolete Fix Me in main.c due to not included header file
Date: Tue, 25 Nov 2014 07:24:02 +0100	[thread overview]
Message-ID: <20141125062402.GA17059@gmail.com> (raw)
In-Reply-To: <5473E8BD.2050105@gmail.com>


* nick <xerofoify@gmail.com> wrote:

> Greeting Thomas and other maintainers, I am wondering why we 
> still need a fix me for including types.h,as this seems correct 
> and good according to my reading of the other header files this 
> file needs to function. Nick

So your first few mails were OK, but now you are coming close to 
a dozen emails in my mbox alone, and the thing is, there's over 
4,000 FIXME's in the kernel source:

  comet:~/tip> git grep -i FIXME | wc -l
  4415

These FIXME's are there to warn active developers about issues to 
work on - and they generally get removed when that code gets 
fixed or changes later on, typically without generating any 
separate commit. (Sometimes they don't get removed for a longer 
time - there's not much harm as eventually they will be removed.)

In other words: please stop this stream of mostly pointless 
emails! Instead of generating 4,000+ additional emails, please 
try to find some real bug to work on?

Thanks,

	Ingo

           reply	other threads:[~2014-11-25  6:24 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5473E8BD.2050105@gmail.com>]

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=20141125062402.GA17059@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@suse.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xerofoify@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.