All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhijit Chandrakant Pawar <abhi.c.pawar@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: SMR Project List
Date: Tue, 28 Jan 2014 14:00:36 +0530	[thread overview]
Message-ID: <52E76AAC.7090803@gmail.com> (raw)
In-Reply-To: <nsxbnyxii32.fsf@closure.home.lan>

Hi Ted,

On Monday 27 January 2014 08:32 PM, Theodore Ts'o wrote:
> I've been putting together a list of potential work items that would
> help improve Linux's support for SMR drives.
> 
> Currently it's for brain storming purposes only, but later on we might
> use this so we can better coordinate efforts across engineers at
> different companies, in terms of avoiding duplicating work and making
> sure we understand dependencies and gaps.
> 
> My intention is to have this to be a community-edited document.  If you
> are interested in making any changes, please let me know and send me a
> Google account id (i.e., GMail address, etc.).  Anyone can make comments
> on the spreadsheet, so if you'd like to do that, feel free.
> 
> Cheers!
> 
>                                                 - Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

I would be happy to contribute to this. My email id is:
abhi.c.pawar@gmail.com

Regards,
Abhijit Pawar

      parent reply	other threads:[~2014-01-28  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 15:02 SMR Project List Theodore Ts'o
2014-01-27 16:42 ` Zheng Liu
2014-01-27 16:54 ` Carlos Maiolino
2014-01-28  4:04 ` Prasad Joshi
2014-01-28  6:17 ` Jaegeuk Kim
2014-01-28  6:45 ` Zhi Yong Wu
2014-01-28  7:55 ` Rohan Puri
2014-01-28  8:30 ` Abhijit Chandrakant Pawar [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=52E76AAC.7090803@gmail.com \
    --to=abhi.c.pawar@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 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.