From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alan Cox <alan@linux.intel.com>, Feng Tang <feng.tang@intel.com>,
linux-kernel@vger.kernel.org, greg@kroah.com, x86@kernel.org
Subject: Re: [PATCH v3 1/4] x86, mrst: make mrst_identify_cpu() inlne inside mrst.h
Date: Wed, 15 Sep 2010 10:24:29 +0200 [thread overview]
Message-ID: <20100915082429.GB16593@elte.hu> (raw)
In-Reply-To: <20100914205044.03ba679b@lxorguk.ukuu.org.uk>
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Tue, 14 Sep 2010 19:57:26 +0200
> Ingo Molnar <mingo@elte.hu> wrote:
>
> >
> > * Alan Cox <alan@linux.intel.com> wrote:
> >
> > > On Mon, 13 Sep 2010 15:08:53 +0800
> > > Feng Tang <feng.tang@intel.com> wrote:
> > >
> > > > Otherwise there will be some compilation warning for those .c files
> > > > which include mrst.h
> > >
> > > I've sent this to Ingo four or five times already and been ignored.
> >
> > I did a search of my mbox for all mails containing
> > 'mrst_identify_cpu', and the one by Feng Tang sent yesterday is the
> > only one - none from you. Searched the spam folder and the separate
> > lkml folder too.
> >
> > So where are those 4-5 emails, got any link perhaps?
>
> They went to your address and my logs show they hit Intel internally
> but I can't really see beyond that - I've mailed you directly a
> different email to try and work out where they vanished so if you see
> this and no direct mail then that would explain much. If you see both
> but didn't see the mail recently about SFI device creation from me
> then it's specific to the stgit setup sent emails.
I think there must be an email problem somewhere. I did get the:
[RFC PATCH] x86/mrst: add SFI platform device parsing code
mail and the earlyprintk mails - but before that the only patch i got
from you was:
[PATCH] IPC driver for Intel Mobile Internet Device (MID) platforms
back in April ... i.e. nothing for many months.
Thanks,
Ingo
next prev parent reply other threads:[~2010-09-15 8:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 7:08 [PATCH v3 0/4] Enabling patches of 2 early consoles for Intel MID platforms Feng Tang
2010-09-13 7:08 ` [PATCH v3 1/4] x86, mrst: make mrst_identify_cpu() inlne inside mrst.h Feng Tang
2010-09-14 13:43 ` Alan Cox
2010-09-14 17:57 ` Ingo Molnar
2010-09-14 19:50 ` Alan Cox
2010-09-15 8:24 ` Ingo Molnar [this message]
2010-09-13 7:08 ` [PATCH v3 2/4] x86: add two helper macros for fixed address mapping Feng Tang
2010-10-08 10:52 ` [tip:x86/mrst] x86: Add " tip-bot for Feng Tang
2010-09-13 7:08 ` [PATCH v3 3/4] x86, earlyprintk: add earlyprintk for Intel Moorestown platform Feng Tang
2010-10-08 10:53 ` [tip:x86/mrst] x86, earlyprintk: Add " tip-bot for Feng Tang
2010-09-13 7:08 ` [PATCH v3 4/4] x86, earlyprintk: add hsu early console for Intel Medfield platform Feng Tang
2010-09-21 16:26 ` Konrad Rzeszutek Wilk
2010-09-23 10:08 ` Alan Cox
2010-10-08 10:53 ` [tip:x86/mrst] x86, earlyprintk: Add " tip-bot for Feng Tang
2010-09-13 8:40 ` [PATCH v3 0/4] Enabling patches of 2 early consoles for Intel MID platforms Ingo Molnar
2010-09-13 16:59 ` Greg KH
2010-09-13 18:43 ` Ingo Molnar
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=20100915082429.GB16593@elte.hu \
--to=mingo@elte.hu \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=feng.tang@intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®