public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: updating mtime for char/block devices?
Date: Tue, 1 Mar 2005 11:19:22 +0000	[thread overview]
Message-ID: <20050301111922.B29817@flint.arm.linux.org.uk> (raw)
In-Reply-To: <42244EDD.9020204@gmx.net>; from c-d.hailfinger.devel.2005@gmx.net on Tue, Mar 01, 2005 at 12:15:41PM +0100

On Tue, Mar 01, 2005 at 12:15:41PM +0100, Carl-Daniel Hailfinger wrote:
> Russell King schrieb:
> > tty mtime updates aren't marked dirty, so aren't written back to disk.
> > Intentionally.
> 
> It seems the tty mtime exception doesn't include /dev/ptmx. That's
> probably unintentional. Is there a chance to extend the tty mtime
> exception to all char devices or at least major 4+5?

It does include /dev/ptmx, at least here with 2.6.11-rc2-bk1 and 2.4
kernels.  In fact, it's common to all tty devices since it's handled
by the generic tty code.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

      reply	other threads:[~2005-03-01 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 23:51 updating mtime for char/block devices? Carl-Daniel Hailfinger
2005-02-28  7:47 ` Arjan van de Ven
2005-03-01  0:45   ` Carl-Daniel Hailfinger
2005-03-01  1:47     ` Valdis.Kletnieks
2005-03-01  9:37     ` Russell King
2005-03-01 11:15       ` Carl-Daniel Hailfinger
2005-03-01 11:19         ` Russell King [this message]

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=20050301111922.B29817@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=arjan@infradead.org \
    --cc=c-d.hailfinger.devel.2005@gmx.net \
    --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