From: Greg KH <gregkh@linuxfoundation.org>
To: Tejun Heo <tj@kernel.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, JBottomley@parallels.com,
bhelgaas@google.com
Subject: Re: [PATCHSET v2 driver-core-next] kernfs, sysfs, driver-core: implement synchronous self-removal
Date: Sat, 11 Jan 2014 12:19:09 -0800 [thread overview]
Message-ID: <20140111201909.GA30380@kroah.com> (raw)
In-Reply-To: <20140111185110.GB3257@mtj.dyndns.org>
On Sat, Jan 11, 2014 at 01:51:10PM -0500, Tejun Heo wrote:
> Hey, Alan.
>
> On Fri, Jan 10, 2014 at 10:46:10AM -0500, Alan Stern wrote:
> > The SUBJECT lines in your patch emails don't mention the version
> > number. That is, they just say "[PATCH]", not "[PATCH v2]" or "[PATCH
> > v3]". This makes it very difficult for me to tell which messages to
> > read.
>
> Hmm... they're all threaded. I add version tags when posting
> incremental patches but usually don't bother with it when posting a
> new version of the whole series. After all, some patches are get
> updated without explicitly given a new version for refrehses and stuff
> so it's not like you can determine everything based on subjects only.
>
> > (Reading them in order doesn't work, because my computer mixes up the
> > order of messages when it downloads a large bunch from the email
> > server. It's kind of annoying...)
>
> And they aren't threaded?
They were all threaded for me, perhaps Alan needs a better email client :)
next prev parent reply other threads:[~2014-01-11 20:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 13:46 [PATCHSET v2 driver-core-next] kernfs, sysfs, driver-core: implement synchronous self-removal Tejun Heo
2014-01-10 13:46 ` [PATCH 01/14] kernfs: fix get_active failure handling in kernfs_seq_*() Tejun Heo
2014-01-10 13:46 ` [PATCH 02/14] kernfs: replace kernfs_node->u.completion with kernfs_root->deactivate_waitq Tejun Heo
2014-01-10 13:46 ` [PATCH 03/14] kernfs: remove KERNFS_ACTIVE_REF and add kernfs_lockdep() Tejun Heo
2014-01-10 13:46 ` [PATCH 04/14] kernfs: remove KERNFS_REMOVED Tejun Heo
2014-01-10 13:46 ` [PATCH 05/14] kernfs: restructure removal path to fix possible premature return Tejun Heo
2014-01-10 13:46 ` [PATCH 06/14] kernfs: invoke kernfs_unmap_bin_file() directly from __kernfs_remove() Tejun Heo
2014-01-10 13:46 ` [PATCH 07/14] kernfs: remove kernfs_addrm_cxt Tejun Heo
2014-01-10 13:46 ` [PATCH 08/14] kernfs: make kernfs_get_active() block if the node is deactivated but not removed Tejun Heo
2014-01-10 13:46 ` [PATCH 09/14] kernfs: implement kernfs_{de|re}activate[_self]() Tejun Heo
2014-01-10 13:46 ` [PATCH 10/14] kernfs, sysfs, driver-core: implement kernfs_remove_self() and its wrappers Tejun Heo
2014-01-10 13:46 ` [PATCH 11/14] pci: use device_remove_file_self() instead of device_schedule_callback() Tejun Heo
2014-01-10 13:46 ` [PATCH 12/14] scsi: " Tejun Heo
2014-01-10 13:46 ` [PATCH 13/14] s390: " Tejun Heo
2014-01-10 13:47 ` [PATCH 14/14] sysfs, driver-core: remove unused {sysfs|device}_schedule_callback_owner() Tejun Heo
2014-01-10 13:54 ` [PATCHSET v2 driver-core-next] kernfs, sysfs, driver-core: implement synchronous self-removal Tejun Heo
2014-01-10 15:46 ` Alan Stern
2014-01-11 18:51 ` Tejun Heo
2014-01-11 20:19 ` Greg KH [this message]
2014-01-11 22:52 ` Alan Stern
2014-01-11 23:37 ` Greg KH
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=20140111201909.GA30380@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=JBottomley@parallels.com \
--cc=bhelgaas@google.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=stern@rowland.harvard.edu \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.