From: Alexander van Heukelum <heukelum@fastmail.fm>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Borislav Petkov <bp@suse.de>,
Andy Lutomirski <luto@amacapital.net>, X86 ML <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Oleg Nesterov <oleg@redhat.com>, Rik van Riel <riel@redhat.com>,
Denys Vlasenko <dvlasenk@redhat.com>
Subject: Re: [PATCHv2 0/4] x86, entry: some cleanup and simplification...
Date: Wed, 21 Jan 2015 16:51:59 +0100 [thread overview]
Message-ID: <1421855519.163242.216784957.65B8D9AF@webmail.messagingengine.com> (raw)
In-Reply-To: <CAK1hOcNG8AfAa=m_KTPSV7fZWcymiXAeZrcwmtThowM-eafc7g@mail.gmail.com>
On Wed, Jan 21, 2015, at 14:26, Denys Vlasenko wrote:
> On Sun, Jan 18, 2015 at 4:47 PM, Alexander van Heukelum
> <heukelum@fastmail.fm> wrote:
> > On Sun, Jan 18, 2015, at 13:05, Borislav Petkov wrote:
> >> Hi,
> >>
> >> btw, you might wanna sync with Denys who's doing cleanups in that area too:
> >>
> >> https://lkml.kernel.org/r/1421272101-16847-1-git-send-email-dvlasenk@redhat.com
> >>
> >> and touching some of the stuff you're changing too.
> >
> > Thanks. FWIW, the change touches the same area in code, but is orthogonal in concept.
>
> My patches eventually eliminate both ARGOFFSET and KERNEL_STACK_OFFSET.
> For example, eventually TI_flags tests look like this after all my patches:
>
> testl $const, TI_flags+THREAD_INFO(%rsp,SIZEOF_PTREGS)
>
> Your patches massage the same defines in a different way than mine do.
> We clearly have a conflict here.
Indeed. I missed that, because Borislav's link only pointed to a single
change and I failed to notice the "[01/11]" in the title.
prev parent reply other threads:[~2015-01-21 15:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 11:45 Alexander van Heukelum
2015-01-18 11:45 ` [PATCHv2 1/4] x86_64: cleanup THREAD_INFO(reg,offset) macro Alexander van Heukelum
2015-01-21 13:40 ` Denys Vlasenko
2015-01-21 16:20 ` Alexander van Heukelum
2015-01-21 18:04 ` Borislav Petkov
2015-01-21 18:48 ` Alexander van Heukelum
2015-01-18 11:45 ` [PATCHv2 2/4] x86_64: embrace KERNEL_STACK_OFFSET Alexander van Heukelum
2015-01-21 13:44 ` Denys Vlasenko
2015-01-21 16:29 ` Alexander van Heukelum
2015-01-23 0:53 ` Denys Vlasenko
2015-01-18 11:45 ` [PATCHv2 3/4] i386: clean up KERNEL_STACK_OFFSET Alexander van Heukelum
2015-01-18 11:45 ` [PATCHv2 4/4] x86_64, entry: Create IRET-compatible stack frame at syscall entry Alexander van Heukelum
2015-01-18 16:38 ` Andy Lutomirski
2015-01-18 17:22 ` Alexander van Heukelum
2015-01-18 12:05 ` [PATCHv2 0/4] x86, entry: some cleanup and simplification Borislav Petkov
2015-01-18 15:47 ` Alexander van Heukelum
2015-01-21 13:26 ` Denys Vlasenko
2015-01-21 15:51 ` Alexander van Heukelum [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=1421855519.163242.216784957.65B8D9AF@webmail.messagingengine.com \
--to=heukelum@fastmail.fm \
--cc=bp@suse.de \
--cc=dvlasenk@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=riel@redhat.com \
--cc=vda.linux@googlemail.com \
--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®