public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hpet, allow user controlled mmap for user processes
Date: Tue, 19 Mar 2013 15:51:05 +0100	[thread overview]
Message-ID: <51487B59.6010607@ladisch.de> (raw)
In-Reply-To: <5148747C.9020803@redhat.com>

Prarit Bhargava wrote:
> On 03/19/2013 03:43 AM, Clemens Ladisch wrote:
>> Prarit Bhargava wrote:
>>> +	int "Enable HPET MMAP access by default"
>>> +	default 0
>>
>> This breaks backwards compatibility.
>
> Does backwards compatibility matter for something like?  I have no problem
> setting it to 1 but I'm more curious from a general kernel point of view.

When somebody updates from some old kernel where HPET mmap was
explicitly enabled, this default value will now disable it.  The
default behaviour should always be to be compatible with older
kernels.


Regards,
Clemens

  reply	other threads:[~2013-03-19 14:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 20:00 [PATCH] hpet, allow user controlled mmap for user processes Prarit Bhargava
2013-03-16  9:54 ` Clemens Ladisch
2013-03-18 12:24   ` Prarit Bhargava
2013-03-19  7:43     ` Clemens Ladisch
2013-03-19 14:21       ` Prarit Bhargava
2013-03-19 14:51         ` Clemens Ladisch [this message]
2013-03-22 13:32           ` Prarit Bhargava
2013-08-29  6:01             ` Matt Wilson
2013-09-13  0:00               ` Prarit Bhargava
2013-09-29 20:28                 ` [PATCH] hpet: " Clemens Ladisch
2013-03-19 14:49       ` [PATCH] hpet, " Prarit Bhargava

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=51487B59.6010607@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prarit@redhat.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