public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tridge@samba.org
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Jan Engelhardt <jengelh@medozas.de>, Theodore Tso <tytso@mit.edu>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Pavel Machek <pavel@ucw.cz>, Jamie Lokier <jamie@shareable.org>,
	john.lanza@linux.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org,
	Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
	corbet@lwn.net, jcm@jonmasters.org, Paul.McKenney@us.ibm.com
Subject: VFAT patent workaround - patches and tree on kernel.org
Date: Sat, 11 Jul 2009 12:49:18 +1000	[thread overview]
Message-ID: <19031.64942.968563.614697@samba.org> (raw)

Thanks to everyone for the lively debate on this patch. If nothing
else it has served to highlight the issue of whether the Linux kernel
should incorporate patent workarounds. The open debate on this has
been very valuable I think.

Thank you also to Hirofumi-san for taking the time to consider my
proposed patch. It was an exhausting debate, and I appreciate the
effort that Hirofumi-san has put in to read through such complex
arguments.

I have created a directory on kernel.org containing the patch, and a
README which documents the interoperability concerns that were raised
during the discussion of the patch:

  http://kernel.org/pub/linux/kernel/people/tridge/VFAT/

I have also created a git tree incorporating the patch, based on the
fatfs-2.6 tree:

  http://git.kernel.org/?p=linux/kernel/git/tridge/fatfs-dualnames.git

Hirofumi-san, could you look at
04f4db5202d2d3ec9b8e780b913c1f1dd3881745 in my tree and consider that
separately for inclusion in your tree?

The patch is also available here:

  http://git.kernel.org/?p=linux/kernel/git/tridge/fatfs-dualnames.git;a=commitdiff;h=04f4db5202d2d3ec9b8e780b913c1f1dd3881745

I will continue to try to address the technical concerns that have
been raised. I appreciate the testing that has been done by many
people on this list, and I hope that testing will continue. 

If I am able to make substantial progress on the technical issues that
have been raised then I will re-submit the patch for consideration for
inclusion in the upstream kernel.

Cheers, Tridge

                 reply	other threads:[~2009-07-11  2:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=19031.64942.968563.614697@samba.org \
    --to=tridge@samba.org \
    --cc=Paul.McKenney@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=corbet@lwn.net \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jamie@shareable.org \
    --cc=jcm@jonmasters.org \
    --cc=jengelh@medozas.de \
    --cc=john.lanza@linux.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rusty@rustcorp.com.au \
    --cc=shaggy@linux.vnet.ibm.com \
    --cc=tytso@mit.edu \
    /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