linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Graeme Sheppard <nodes@rillion.net>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: Patent or not patent a new idea
Date: Tue, 26 Jun 2007 09:45:22 +1200	[thread overview]
Message-ID: <46803772.7020408@rillion.net> (raw)

Dear devs,

In a moment of serendipity I thought of a concept which may be advantageous
if incorporated into the kernel. I was going to offer it to the OIN but
they responded they only consider existing patents and I don't have the
money to afford one.

I am seeking advice on how to proceed. It could be used as a defensive
patent in which case I can email an expert who can file it. If that is the
concept is sound. I am not expecting any royalties from this myself. The
alternative is to dump it here to the LKML.

It should be said I'm not a kernel coder and if I attempted this I would
probably do it wrong. The concept is a different way to attain performance.
The area pertaining is filesystems.

Not wishing to overstate things lest the flames scorching a bad idea get
too hot.

Regards,
Graeme

             reply	other threads:[~2007-06-25 21:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 21:45 Graeme Sheppard [this message]
2007-06-25 22:04 ` Patent or not patent a new idea alan
2007-06-25 22:26   ` Graeme Sheppard
2007-06-25 22:33     ` alan
2007-06-25 22:34 ` Attila Kinali
2007-06-25 22:37 ` manningc2
2007-06-26  0:11   ` Bryan Henderson
2007-06-26  1:32 ` Graeme Sheppard
2007-06-26  2:20   ` Neil Brown
2007-06-26  3:20     ` Graeme Sheppard
2007-06-26  3:38       ` Neil Brown
2007-06-26  4:22         ` Graeme Sheppard
2007-06-26  4:33           ` Neil Brown
2007-06-26 16:53         ` Bryan Henderson
2007-06-26 17:38           ` Andreas Dilger

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=46803772.7020408@rillion.net \
    --to=nodes@rillion.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.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).