All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <jbottomley@parallels.com>,
	linux-scsi@vger.kernel.org, Jeremy Linton <jlinton@tributary.com>,
	Kay Sievers <kay@vrfy.org>, Doug Gilbert <dgilbert@interlog.com>,
	Kai Makisara <kai.makisara@kolumbus.fi>
Subject: Re: [PATCH 2/3] Add EVPD page 0x83 to sysfs
Date: Fri, 07 Mar 2014 11:35:34 +0100	[thread overview]
Message-ID: <5319A0F6.8000100@suse.de> (raw)
In-Reply-To: <20140307101118.GA32333@infradead.org>

On 03/07/2014 11:11 AM, Christoph Hellwig wrote:
> On Thu, Mar 06, 2014 at 10:01:05AM +0100, Hannes Reinecke wrote:
>> I am somewhat reluctant here.
>>
>> Adding separate flags like 'support_vpd_pg83' is a bit pointless,
>> given that we might as well check for vpg_pg83.
>>
>> So the only 'proper' solution would be to add a bitmap of supported
>> pages; however, this would be 256 bits = 32 bytes of additional
>> space required for struct sdev.
>> Which I'm a bit reluctant do to, as it'll be a sparse array in most
>> cases, adding to quite some wasted space.
> 
> Might want to keep it a local bitmap for now, but I suspect we'll
> want it exposed sooner or later.
> 
Agree. But for now I'd like to keep it as it is (ie without bitmap);
there is no real benefit for just the two pages we're exposing right
now.

Or, to be precise, we _might_ be exporting if those patches ever go
upstream :-(

Having any indication here would be good.
Can't we have a patch handling session at LSF?
It really is no fun, having tons of patches and no idea whether they
ever make it upstream.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-03-07 10:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 10:07 [PATCHv7 0/3] Display EVPD pages in sysfs Hannes Reinecke
2014-02-13 10:07 ` [PATCH 1/3] scsi_sysfs: Implement 'is_visible' callback Hannes Reinecke
2014-02-13 10:07 ` [PATCH 2/3] Add EVPD page 0x83 to sysfs Hannes Reinecke
2014-02-28 17:01   ` Christoph Hellwig
2014-03-05  7:38     ` Hannes Reinecke
2014-03-05 19:42       ` Christoph Hellwig
2014-03-06  9:01         ` Hannes Reinecke
2014-03-07 10:11           ` Christoph Hellwig
2014-03-07 10:35             ` Hannes Reinecke [this message]
2014-03-07 10:44               ` Christoph Hellwig
2014-03-07 10:39           ` James Bottomley
2014-03-07 10:51             ` Hannes Reinecke
2014-03-07 11:01               ` James Bottomley
2014-03-07 11:18                 ` Douglas Gilbert
2014-03-07 13:39                 ` Hannes Reinecke
2014-03-07 10:40           ` James Bottomley
2014-03-07 10:43             ` Christoph Hellwig
2014-03-07 10:57               ` James Bottomley
2014-02-13 10:07 ` [PATCH 3/3] Add EVPD page 0x80 " Hannes Reinecke
  -- strict thread matches above, loose matches on Subject: below --
2014-02-13 10:27 [PATCHv7 0/3][Resend] Display EVPD pages in sysfs Hannes Reinecke
2014-02-13 10:28 ` [PATCH 2/3] Add EVPD page 0x83 to sysfs Hannes Reinecke
2014-03-02  8:34   ` Bart Van Assche
2014-03-05  7:56     ` Hannes Reinecke
2014-03-02  8:36   ` Bart Van Assche
2014-03-05  7:56     ` Hannes Reinecke

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=5319A0F6.8000100@suse.de \
    --to=hare@suse.de \
    --cc=dgilbert@interlog.com \
    --cc=hch@infradead.org \
    --cc=jbottomley@parallels.com \
    --cc=jlinton@tributary.com \
    --cc=kai.makisara@kolumbus.fi \
    --cc=kay@vrfy.org \
    --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.