All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] libata: Prepare for hard drives w/ non-512 sector sizes
Date: Wed, 8 Apr 2009 13:13:59 -0600	[thread overview]
Message-ID: <20090408191359.GM20983@parisc-linux.org> (raw)
In-Reply-To: <49DCF61E.2000703@garzik.org>

On Wed, Apr 08, 2009 at 03:08:14PM -0400, Jeff Garzik wrote:
> Matthew Wilcox wrote:
> >?!  Are you referring to the one incident where you asked me if I had
> >any patches for 2.6.30, I pointed at the TRIM patches and you quibbled
> >that I hadn't reposted the updates, only a git tree?
> 
> On multiple occasions.  You're the only one I have to poke to get 
> updates on pending libata patches, in some cases, patches that really 
> should have gone upstream long ago.

I send patches and get no feedback from the maintainer (you).  So I
work on other things instead.  The 4k sector size support is largely
theoretical anyway, given that every _SATA_ vendor I've heard from is
planning on doing 4k physical / 512 byte logical sectors.  SAS is a
different matter, but is irrelevant to this series of patches.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

      reply	other threads:[~2009-04-08 19:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  6:59 [PATCH] libata: Prepare for hard drives w/ non-512 sector sizes Jeff Garzik
2009-04-08 18:32 ` Matthew Wilcox
2009-04-08 18:47   ` Jeff Garzik
2009-04-08 18:56     ` Matthew Wilcox
2009-04-08 19:08       ` Jeff Garzik
2009-04-08 19:13         ` Matthew Wilcox [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=20090408191359.GM20983@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.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 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.