All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Hannes Reinecke <hare@suse.de>
Cc: Mark Hounschell <dmarkh@cfl.rr.com>,
	linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] sd: Disable support for 256 byte/sector disks
Date: Wed, 13 May 2015 10:29:21 -0400	[thread overview]
Message-ID: <55535FC1.90304@compro.net> (raw)
In-Reply-To: <1431526662.2363.22.camel@HansenPartnership.com>

On 05/13/2015 10:17 AM, James Bottomley wrote:
> On Wed, 2015-05-13 at 16:09 +0200, Hannes Reinecke wrote:
>> On 05/13/2015 04:00 PM, James Bottomley wrote:
>>> On Wed, 2015-05-13 at 10:49 +0200, Hannes Reinecke wrote:
>>>> 256 bytes per sector support has been broken since 2.6.X,
>>>> and no-one stepped up to fix this.
>>>> So disable support for it.
>>>
>>> I assume this should have a
>>>
>>> From: Mark Hounschell <dmarkh@cfl.rr.com>
>>>
>>> at the top?
>>>
>>> James
>>>
>> I wasn't sure, as I've pulled the patch off bugzilla.
>> But do whatever you see fit.
>
> It needs authorship (From: field) of whoever wrote it and put it on
> bugzilla in the first place.  According to the entry, it was him:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=16058#c18
>

I am the author of that patch. What would you like me to do? My home 
email address is what I used in bugzilla "dmarkh@cfl.rr.com" years back 
when I originally submitted the bug. I'm sending this email from work.

I am Mark Hounschell and am the author of that patch and you can do with 
it whatever you see fit?

Regards
Mark



      reply	other threads:[~2015-05-13 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  8:49 [PATCH] sd: Disable support for 256 byte/sector disks Hannes Reinecke
2015-05-13 12:55 ` Mark Hounschell
2015-05-13 14:00 ` James Bottomley
2015-05-13 14:09   ` Hannes Reinecke
2015-05-13 14:17     ` James Bottomley
2015-05-13 14:29       ` Mark Hounschell [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=55535FC1.90304@compro.net \
    --to=markh@compro.net \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dmarkh@cfl.rr.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-scsi@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.