From: Julia Lawall <julia.lawall@lip6.fr>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Christoph Hellwig <hch@lst.de>,
Bhumika Goyal <bhumirks@gmail.com>,
julia.lawall@lip6.fr, rjw@rjwysocki.net, lenb@kernel.org,
alexander.shishkin@linux.intel.com, jic23@kernel.org,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
dledford@redhat.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com, sagi@grimberg.me, kishon@ti.com,
bhelgaas@google.com, nab@linux-iscsi.org, balbi@kernel.org,
gregkh@linuxfoundation.org, jlbec@evilplan.org,
ccaulfie@redhat.com, teigland@redhat.com, mfasheh@versity.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, linux-rdma@vger.kernel.org,
netdev@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-pci@vger.kernel.org, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org, linux-usb@vger.kernel.org,
cluster-devel@redhat.com, ocfs2-devel@oss.oracle.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 02/15] usb: gadget: make config_item_type structures const
Date: Fri, 20 Oct 2017 10:02:46 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1710200857030.2090@hadrien> (raw)
In-Reply-To: <6348630.r2z9ev4yl2@avalon>
On Thu, 19 Oct 2017, Laurent Pinchart wrote:
> Hi Christoph,
>
> On Thursday, 19 October 2017 17:06:57 EEST Christoph Hellwig wrote:
> > > Now we have 9 const instances of the config_item_type structure that are
> > > identical, with only the .ct_owner field set. Should they be all merged
> > > into a single structure ?
> >
> > I think that's a good idea.
> >
> > But I'm about to slurp up this whole series into my tree, how about making
> > that an incremental patch?
>
> I'm fine with that.
>
> Bhumika, would you like to submit an incremental patch, or should I do it ?
For various types, there seem to be a few hundred of these, eg:
static const struct hda_pcm_stream alc269_44k_pcm_analog_playback = {
.rates = SNDRV_PCM_RATE_44100, /* fixed rate */
};
static const struct hda_pcm_stream alc269_44k_pcm_analog_capture = {
.rates = SNDRV_PCM_RATE_44100, /* fixed rate */
};
Would it be desirable to remove them? I guess one would have to check
that there are not any pointer equality checks on these values. Would it
be useful to put a #define to keep the orignal names?
julia
next prev parent reply other threads:[~2017-10-20 8:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 15:18 [PATCH v2 00/15] make structure field, function arguments and structures const Bhumika Goyal
2017-10-16 15:18 ` [PATCH v2 01/15] configfs: make ci_type field, some pointers and function arguments const Bhumika Goyal
2017-10-17 10:24 ` Greg KH
2017-10-16 15:18 ` [PATCH v2 02/15] usb: gadget: make config_item_type structures const Bhumika Goyal
2017-10-17 8:30 ` Felipe Balbi
2017-10-18 16:05 ` Laurent Pinchart
2017-10-19 14:06 ` Christoph Hellwig
2017-10-19 15:05 ` Laurent Pinchart
2017-10-20 8:02 ` Julia Lawall [this message]
2017-10-20 8:13 ` Bhumika Goyal
2017-10-16 15:18 ` [PATCH v2 03/15] target: make config_item_type const Bhumika Goyal
2017-10-16 15:18 ` [PATCH v2 04/15] iio: make function argument and some structures const Bhumika Goyal
2017-10-16 18:48 ` Jonathan Cameron
2017-10-16 15:18 ` [PATCH v2 05/15] ocfs2/cluster: make config_item_type const Bhumika Goyal
2017-10-16 15:18 ` [PATCH v2 06/15] PCI: endpoint: " Bhumika Goyal
2017-10-16 18:24 ` Bjorn Helgaas
2017-10-16 15:18 ` [PATCH v2 07/15] usb: gadget: configfs: " Bhumika Goyal
2017-10-17 8:31 ` Felipe Balbi
2017-10-16 15:18 ` [PATCH v2 08/15] nvmet: " Bhumika Goyal
2017-10-17 10:18 ` Sagi Grimberg
2017-10-16 15:18 ` [PATCH v2 09/15] ACPI: configfs: " Bhumika Goyal
2017-10-17 0:10 ` Rafael J. Wysocki
2017-10-16 15:18 ` [PATCH v2 10/15] nullb: " Bhumika Goyal
2017-10-16 15:18 ` [PATCH v2 11/15] stm class: " Bhumika Goyal
2017-10-17 10:25 ` Greg KH
2017-10-16 15:18 ` [PATCH v2 12/15] RDMA/cma: " Bhumika Goyal
2017-10-17 10:56 ` Leon Romanovsky
2017-10-18 14:33 ` Doug Ledford
2017-10-16 15:18 ` [PATCH v2 13/15] netconsole: " Bhumika Goyal
2017-10-16 15:18 ` [PATCH v2 14/15] dlm: " Bhumika Goyal
2017-10-16 15:18 ` [PATCH v2 15/15] configfs: " Bhumika Goyal
2017-10-17 10:12 ` [PATCH v2 00/15] make structure field, function arguments and structures const Greg KH
2017-10-17 10:16 ` Julia Lawall
2017-10-17 10:23 ` Greg KH
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=alpine.DEB.2.20.1710200857030.2090@hadrien \
--to=julia.lawall@lip6.fr \
--cc=alexander.shishkin@linux.intel.com \
--cc=balbi@kernel.org \
--cc=bhelgaas@google.com \
--cc=bhumirks@gmail.com \
--cc=ccaulfie@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hal.rosenstock@gmail.com \
--cc=hch@lst.de \
--cc=jic23@kernel.org \
--cc=jlbec@evilplan.org \
--cc=kishon@ti.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mfasheh@versity.com \
--cc=nab@linux-iscsi.org \
--cc=netdev@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=pmeerw@pmeerw.net \
--cc=rjw@rjwysocki.net \
--cc=sagi@grimberg.me \
--cc=sean.hefty@intel.com \
--cc=target-devel@vger.kernel.org \
--cc=teigland@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox