public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: fastboot@osdl.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Suparna Bhattacharya <suparna@in.ibm.com>,
	Andy Pfiffer <andyp@osdl.org>
Subject: Re: [KEXEC][2.5.63] Partially tested patches available
Date: 27 Feb 2003 09:01:56 -0700	[thread overview]
Message-ID: <m1wujllnkb.fsf@frodo.biederman.org> (raw)
In-Reply-To: <7350000.1046361606@[10.10.2.4]>

"Martin J. Bligh" <mbligh@aracnet.com> writes:

> >> There were additional syscall hijinks in the merge to 2.5.63, so anyone
> >> that uses this patch set will need to recompile their kexec tools.
> > 
> > Along with all of the usual craziness of life my brother has been
> > staying with me the last month or so, and my amount of free
> > time to actual work on kexec has been less then I like.
> > 
> > We need to get up some steam and see what it will take for Linus
> > to notice and actually get this patch included.
> 
> Could you confirm that the patches are released under the GPL, and have no
> patent encumberances that you know of? That will enable me to integrate
> them and get more people to work on it ...

I though I had.  But yes all of the code is released under GPL version 2
as specified by the kernel copying file.

Eric

  reply	other threads:[~2003-02-27 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26  0:53 [KEXEC][2.5.63] Partially tested patches available Andy Pfiffer
2003-02-27 11:50 ` Eric W. Biederman
2003-02-27 16:00   ` Martin J. Bligh
2003-02-27 16:01     ` Eric W. Biederman [this message]
2003-02-27 16:04       ` Martin J. Bligh
2003-02-28 14:10   ` Bill Davidsen
2003-02-28 17:03     ` Eric W. Biederman
2003-03-02  1:36       ` Werner Almesberger

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=m1wujllnkb.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=andyp@osdl.org \
    --cc=fastboot@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=suparna@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox