linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Mallon <rmallon@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>, walter harms <wharms@bfs.de>,
	Antti Palosaari <crope@iki.fi>,
	kernel-janitors@vger.kernel.org, shubhrajyoti@ti.com,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 13/13] drivers/media/tuners/e4000.c: use macros for i2c_msg initialization
Date: Mon, 08 Oct 2012 08:49:54 +1100	[thread overview]
Message-ID: <5071F902.6050308@gmail.com> (raw)
In-Reply-To: <1349645970.15802.12.camel@joe-AO722>

On 08/10/12 08:39, Joe Perches wrote:
> On Sun, 2012-10-07 at 20:56 +0200, Julia Lawall wrote:
>>>> Some people thought that it would be nice to have the macros rather than
>>>> the inlined field initializations, especially since there is no flag for
>>>> write.  A separate question is whether an array of one element is useful,
>>>> or whether one should systematically use & on a simple variable of the
>>>> structure type.  I'm open to suggestions about either point.
>>>
>>> I think the macro naming is not great.
>>>
>>> Maybe add DEFINE_/DECLARE_/_INIT or something other than an action
>>> name type to the macro names.
>>
>> DEFINE and DECLARE usually have a declared variable as an argument, which 
>> is not the case here.
>>
>> These macros are like the macros PCI_DEVICE and PCI_DEVICE_CLASS.
> 
> I understand that.
> 
>> Are READ and WRITE the action names?  They are really the important 
>> information in this case.
> 
> Yes, most (all?) uses of _READ and _WRITE macros actually
> perform some I/O.

Well, they are describing an IO operation even if they don't perform it
directly. What else would you call them? I think the macro names are
fine as is.

~Ryan


  parent reply	other threads:[~2012-10-07 21:50 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07 15:38 [PATCH 0/11] introduce macros for i2c_msg initialization Julia Lawall
2012-10-07 15:38 ` [PATCH 13/13] drivers/media/tuners/e4000.c: use " Julia Lawall
2012-10-07 16:33   ` walter harms
2012-10-07 16:44     ` Julia Lawall
2012-10-07 17:13       ` walter harms
2012-10-07 17:18         ` Julia Lawall
2012-10-07 18:16           ` Joe Perches
2012-10-07 18:56             ` Julia Lawall
2012-10-07 21:39               ` Joe Perches
2012-10-07 21:43                 ` Julia Lawall
2012-10-07 21:51                   ` Joe Perches
2012-10-08  1:56                     ` Mauro Carvalho Chehab
2012-10-08  2:11                       ` Ryan Mallon
2012-10-08  7:54                         ` Antti Palosaari
2012-10-08  8:31                         ` Julia Lawall
2012-10-09 23:32                           ` Mauro Carvalho Chehab
2012-10-11  6:45                             ` Julia Lawall
2012-12-18 11:46                               ` Jean Delvare
2012-12-18 12:36                                 ` Julia Lawall
2012-12-18 13:13                                   ` Wolfram Sang
2012-10-09 23:50                           ` Mauro Carvalho Chehab
2012-10-08  5:04                     ` Julia Lawall
2012-10-07 21:49                 ` Ryan Mallon [this message]
2012-10-07 21:52       ` Ryan Mallon
2012-10-07 15:38 ` [PATCH 2/13] drivers/media/tuners/mxl5007t.c: " Julia Lawall
2012-10-09 12:30   ` Jean Delvare
2012-10-09 12:50     ` Julia Lawall
2012-10-07 15:38 ` [PATCH 3/13] drivers/media/tuners/qt1010.c: " Julia Lawall
2012-10-07 21:55   ` Ryan Mallon
2012-10-08  5:05     ` Julia Lawall
2012-10-08  5:13       ` Ryan Mallon
2012-10-08  5:24         ` Julia Lawall
2012-10-09 12:12           ` Jean Delvare
2012-10-09 12:51             ` Julia Lawall
2012-10-07 15:38 ` [PATCH 4/13] drivers/media/tuners/tda18212.c: " Julia Lawall
2012-10-07 15:38 ` [PATCH 5/13] drivers/media/tuners: " Julia Lawall
2012-10-07 22:05   ` Ryan Mallon
2012-10-08  5:12     ` Julia Lawall
2012-10-07 15:38 ` [PATCH 6/13] drivers/media/tuners/tda18271-common.c: " Julia Lawall
2012-10-07 15:38 ` [PATCH 7/13] drivers/media/tuners/tua9001.c: " Julia Lawall
2012-10-07 15:38 ` [PATCH 8/13] drivers/media/tuners/fc2580.c: " Julia Lawall
2012-10-07 15:38 ` [PATCH 9/13] drivers/media/tuners/fc0011.c: " Julia Lawall
2012-10-07 16:43   ` walter harms
2012-10-07 16:50     ` Julia Lawall
2012-10-07 16:54       ` walter harms
2012-10-07 18:05       ` Michael Büsch
2012-10-09 12:06       ` Jean Delvare
2012-10-07 15:38 ` [PATCH 10/13] drivers/media/tuners/tda8290.c: " Julia Lawall
2012-10-07 15:38 ` [PATCH 11/13] drivers/media/tuners/tda18218.c: " Julia Lawall
2012-10-07 15:38 ` [PATCH 12/13] drivers/media/tuners/max2165.c: " Julia Lawall
2012-10-07 22:14   ` Ryan Mallon
2012-10-08  5:13     ` Julia Lawall
2012-10-09 15:32 ` [PATCH 0/11] introduce " Jean Delvare
2012-10-09 15:43   ` Julia Lawall
2012-10-22  9:18   ` Julia Lawall

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=5071F902.6050308@gmail.com \
    --to=rmallon@gmail.com \
    --cc=crope@iki.fi \
    --cc=joe@perches.com \
    --cc=julia.lawall@lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=shubhrajyoti@ti.com \
    --cc=wharms@bfs.de \
    /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;
as well as URLs for NNTP newsgroup(s).