From: Joe Perches <joe@perches.com>
To: "Leonid V. Fedorenchik" <leonidsbox@gmail.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org, mchehab@redhat.com,
arnd@arndb.de, linux-kernel@vger.kernel.org,
Palash.Bandyopadhyay@conexant.com, ruslan@rpisarev.org.ua,
Revent82@gmail.com
Subject: Re: [PATCH] Staging: cx25821: fix coding style issues
Date: Mon, 01 Aug 2011 09:14:22 -0700 [thread overview]
Message-ID: <1312215262.11635.15.camel@Joe-Laptop> (raw)
In-Reply-To: <1312191229-24718-1-git-send-email-leonidsbox@gmail.com>
On Mon, 2011-08-01 at 17:33 +0800, Leonid V. Fedorenchik wrote:
> Fix too long lines in cx25821-audio.h and cx25821-core.c
[]
> diff --git a/drivers/staging/cx25821/cx25821-core.c b/drivers/staging/cx25821/cx25821-core.c
[]
> @@ -972,8 +972,8 @@ static int cx25821_dev_setup(struct cx25821_dev *dev)
> dev->lmmio = ioremap(dev->base_io_addr, pci_resource_len(dev->pci, 0));
>
> if (!dev->lmmio) {
> - CX25821_ERR
> - ("ioremap failed, maybe increasing __VMALLOC_RESERVE in page.h\n");
> + CX25821_ERR("ioremap failed, maybe increasing __VMALLOC_RESERVE"
> + " in page.h\n");
Please do not split formats.
> cx25821_iounmap(dev);
> return -ENOMEM;
> }
> @@ -1011,8 +1011,8 @@ static int cx25821_dev_setup(struct cx25821_dev *dev)
> if (video_register_device
> (dev->ioctl_dev, VFL_TYPE_GRABBER, VIDEO_IOCTL_CH) < 0) {
> cx25821_videoioctl_unregister(dev);
> - pr_err("%s(): Failed to register video adapter for IOCTL, so unregistering videoioctl device\n",
> - __func__);
> + pr_err("%s(): Failed to register video adapter for IOCTL, so "
> + "unregistering videoioctl device\n", __func__);
This was better before the change.
> -static struct pci_device_id cx25821_pci_tbl[] = {
> +static DEFINE_PCI_DEVICE_TABLE(cx25821_pci_tbl) __used = {
__used? Hard to believe that's necessary here.
next prev parent reply other threads:[~2011-08-01 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 9:33 [PATCH] Staging: cx25821: fix coding style issues Leonid V. Fedorenchik
2011-08-01 16:14 ` Joe Perches [this message]
2011-08-02 9:18 ` Leonid V. Fedorenchik
2011-08-02 11:42 ` Mauro Carvalho Chehab
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=1312215262.11635.15.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=Palash.Bandyopadhyay@conexant.com \
--cc=Revent82@gmail.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=leonidsbox@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=ruslan@rpisarev.org.ua \
/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