public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: gregkh@linuxfoundation.org
Cc: kay@vrfy.org, linux-kernel@vger.kernel.org, ebiederm@xmission.com
Subject: Re: [PATCHSET] sysfs: use seq_file and unify regular and bin file handling
Date: Sat, 28 Sep 2013 18:15:13 -0400	[thread overview]
Message-ID: <20130928221513.GA20640@htj.dyndns.org> (raw)
In-Reply-To: <1380404984-31858-1-git-send-email-tj@kernel.org>

Hey, again.

On Sat, Sep 28, 2013 at 05:49:30PM -0400, Tejun Heo wrote:
>  0001-sysfs-remove-unused-sysfs_buffer-pos.patch
>  0002-sysfs-remove-sysfs_buffer-needs_read_fill.patch
>  0003-sysfs-remove-sysfs_buffer-ops.patch
>  0004-sysfs-add-sysfs_open_file_mutex.patch
>  0005-sysfs-rename-sysfs_buffer-to-sysfs_open_file.patch
>  0006-sysfs-add-sysfs_open_file-sd-and-file.patch
>  0007-sysfs-use-transient-write-buffer.patch
>  0008-sysfs-use-seq_file-when-reading-regular-files.patch
>  0009-sysfs-prepare-llseek-path-for-unified-regular-bin-fi.patch
>  0010-sysfs-prepare-path-write-for-unified-regular-bin-fil.patch
>  0011-sysfs-prepare-read-path-for-unified-regular-bin-file.patch
>  0012-sysfs-copy-bin-mmap-support-from-fs-sysfs-bin.c-to-f.patch
>  0013-sysfs-prepare-open-path-for-unified-regular-bin-file.patch
>  0014-sysfs-merge-regular-and-bin-file-handling.patch

On the second thought, 0011 seems too dangerous, especially for pci IO
BAR regions.  Grumble, looks like I'll have to break out the bin read
path.  Please ignore patches >= 0009.  I'll update them and repost.

Thanks!

-- 
tejun

  parent reply	other threads:[~2013-09-28 22:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28 21:49 [PATCHSET] sysfs: use seq_file and unify regular and bin file handling Tejun Heo
2013-09-28 21:49 ` [PATCH 01/14] sysfs: remove unused sysfs_buffer->pos Tejun Heo
2013-09-28 21:49 ` [PATCH 02/14] sysfs: remove sysfs_buffer->needs_read_fill Tejun Heo
2013-09-28 21:49 ` [PATCH 03/14] sysfs: remove sysfs_buffer->ops Tejun Heo
2013-09-28 21:49 ` [PATCH 04/14] sysfs: add sysfs_open_file_mutex Tejun Heo
2013-09-28 21:49 ` [PATCH 05/14] sysfs: rename sysfs_buffer to sysfs_open_file Tejun Heo
2013-09-28 21:49 ` [PATCH 06/14] sysfs: add sysfs_open_file->sd and ->file Tejun Heo
2013-09-28 21:49 ` [PATCH 07/14] sysfs: use transient write buffer Tejun Heo
2013-09-28 21:49 ` [PATCH 08/14] sysfs: use seq_file when reading regular files Tejun Heo
2013-09-28 21:49 ` [PATCH 09/14] sysfs: prepare llseek path for unified regular / bin file handling Tejun Heo
2013-09-28 21:49 ` [PATCH 10/14] sysfs: prepare path write " Tejun Heo
2013-09-28 21:49 ` [PATCH 11/14] sysfs: prepare read path " Tejun Heo
2013-09-28 21:49 ` [PATCH 12/14] sysfs: copy bin mmap support from fs/sysfs/bin.c to fs/sysfs/file.c Tejun Heo
2013-09-28 21:49 ` [PATCH 13/14] sysfs: prepare open path for unified regular / bin file handling Tejun Heo
2013-09-28 21:49 ` [PATCH 14/14] sysfs: merge regular and " Tejun Heo
2013-09-28 22:15 ` Tejun Heo [this message]
2013-09-30 19:54   ` [PATCHSET] sysfs: use seq_file and unify " Tejun Heo
2013-09-30 20:14     ` Greg KH
2013-10-01  5:03   ` Bjorn Helgaas
2013-10-01 14:23     ` Tejun Heo

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=20130928221513.GA20640@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kay@vrfy.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