From: viro@ZenIV.linux.org.uk
To: Andrew Morton <akpm@osdl.org>
Cc: zippel@linux-m68k.org, linux-kernel@vger.kernel.org,
viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [PATCH 0/10] m68k/thread_info merge
Date: Fri, 2 Sep 2005 03:57:46 +0100 [thread overview]
Message-ID: <20050902025746.GE26264@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20050901171738.49d8893d.akpm@osdl.org>
On Thu, Sep 01, 2005 at 05:17:38PM -0700, Andrew Morton wrote:
> Andrew Morton <akpm@osdl.org> wrote:
> >
> > Can I assume that the five m68k patches can be split apart from the five
> > patches which dink with task_struct? ie: if the task_struct patches go in
> > later, does anything bad happen?
>
> eh, forget I asked that. They're interdependent.
... but do not have to be.
next prev parent reply other threads:[~2005-09-02 2:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 21:56 [PATCH 0/10] m68k/thread_info merge Roman Zippel
2005-09-02 0:16 ` Andrew Morton
2005-09-02 0:17 ` Andrew Morton
2005-09-02 2:57 ` viro [this message]
2005-09-02 8:24 ` Roman Zippel
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=20050902025746.GE26264@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=zippel@linux-m68k.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