From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Felix Schnizlein <fschnizlein@suse.com>,
Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Borislav Petkov <bp@alien8.de>
Subject: Re: linux-next: Tree for Sep 19 (x86/kernel/cpuinfo.c)
Date: Tue, 26 Sep 2017 23:18:41 +0200 [thread overview]
Message-ID: <20170926211841.GA28696@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1709261759060.2884@nanos>
On Tue, Sep 26, 2017 at 06:00:44PM +0200, Thomas Gleixner wrote:
> On Tue, 26 Sep 2017, Felix Schnizlein wrote:
> > On 26.09.17, Thomas Gleixner wrote:
> > > > And these patches were posted many times, Felix, you did cc: the arch
> > > > maintainers, right? I don't have access to my archives at the moment...
> > I send all my patches via:
> > git send-email --to linux-kernel@vger.kernel.org --cc x86@kernel.org --cc gregkh@linuxfoundation.org --cc trenn@suse.com v4*.patch
> >
> > Did I miss something?
>
> You missed the fact that this stuff never showed up on LKML and
> interestingly enough it did not make it to x86@k.org either.
Ok, something went really wrong here.
All of the patches of this series are now dropped from my tree entirely.
Felix, please try this again...
thanks,
greg k-h
prev parent reply other threads:[~2017-09-26 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 4:15 linux-next: Tree for Sep 19 Stephen Rothwell
2017-09-19 15:49 ` linux-next: Tree for Sep 19 (drivers/gpu/drm/i915/i915_gem.c) Randy Dunlap
2017-09-19 15:54 ` linux-next: Tree for Sep 19 (x86/kernel/cpuinfo.c) Randy Dunlap
2017-09-26 1:19 ` Randy Dunlap
2017-09-26 7:40 ` Thomas Gleixner
2017-09-26 8:18 ` Greg Kroah-Hartman
2017-09-26 10:40 ` Thomas Gleixner
2017-09-26 12:36 ` Felix Schnizlein
2017-09-26 16:00 ` Thomas Gleixner
2017-09-26 21:18 ` Greg Kroah-Hartman [this message]
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=20170926211841.GA28696@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=fschnizlein@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).