All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Bart Van Assche <Bart.VanAssche@wdc.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] qla2xxx: don't include <generated/utsrelease.h>
Date: Wed, 21 Jun 2017 15:43:14 +0200	[thread overview]
Message-ID: <1498052594.9688.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1498051773.3295.1.camel@wdc.com>

On Wed, 2017-06-21 at 13:29 +0000, Bart Van Assche wrote:
> On Wed, 2017-06-21 at 13:40 +0200, Johannes Berg wrote:
> > From: Johannes Berg <johannes.berg@intel.com>
> > 
> > There's no need to use the static UTS_RELEASE string, since
> > utsname()->release contains the same.
> > 
> > This avoids rebuilding this file for every change of the
> > release string.

> > tcm_qla2xxx_wwn_version_show(struct config_item *item,
> >  		char *page)
> >  {
> >  	return sprintf(page,
> > -	    "TCM QLOGIC QLA2XXX NPIV capable fabric module %s on
> > %s/%s on "
> > -	    UTS_RELEASE"\n", QLA2XXX_VERSION, utsname()->sysname,
> > -	    utsname()->machine);
> > +	    "TCM QLOGIC QLA2XXX NPIV capable fabric module %s on
> > %s/%s on %s\n",
> > +	    QLA2XXX_VERSION, utsname()->sysname,
> > +	    utsname()->machine, utsname()->release);
> >  }

> Although this patch looks fine to me, I think removing the UTS
> release information from the output entirely would be even better. I
> think including that information in the output only made sense before
> LIO went upstream.

Well, yeah, maybe. But at least the part I preserved in the quote above
has userspace API implications, so I really didn't want to do that as a
drive-by patch submission :)

johannes

  reply	other threads:[~2017-06-21 13:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 11:40 [PATCH] qla2xxx: don't include <generated/utsrelease.h> Johannes Berg
2017-06-21 11:43 ` Johannes Thumshirn
2017-06-21 13:29 ` Bart Van Assche
2017-06-21 13:43   ` Johannes Berg [this message]
2017-06-26 17:06 ` Martin K. Petersen

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=1498052594.9688.0.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Bart.VanAssche@wdc.com \
    --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.