From: "Ryan C. Gordon" <icculus@icculus.org>
To: Rayson Ho <raysonlogin@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FatELF & patents
Date: Mon, 26 Oct 2009 14:42:32 -0400 [thread overview]
Message-ID: <4AE5ED98.8090500@icculus.org> (raw)
In-Reply-To: <73a01bf20910261059j74bb37a9td472efc21c5440ca@mail.gmail.com>
> However, there are 20 claims in the patent. Just using a different way
> to store the architecture independent header might not be enough.
I'm not a lawyer, so I don't have anything to add to this except that
FatELF has a few fields that Apple's format doesn't, so the flow chart
they specify isn't the same. I don't really know enough about how
patents work.
Any lawyers around that can comment on this? Is this something to be
concerned with (and if so, what sort of changes would make FatELF not
violate the patent), or is this all just business as usual?
--ryan.
next prev parent reply other threads:[~2009-10-26 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 15:50 FatELF & patents Rayson Ho
2009-10-26 16:01 ` Anton D. Kachalov
2009-10-26 17:59 ` Rayson Ho
2009-10-26 18:42 ` Ryan C. Gordon [this message]
2009-10-26 21:54 ` David Miller
2009-10-26 22:15 ` Rayson Ho
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=4AE5ED98.8090500@icculus.org \
--to=icculus@icculus.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raysonlogin@gmail.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