From: Edward Lipinsky <ellipinsky@gmail.com>
To: Mike Rapoport <mike.rapoport@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-fbdev@vger.kernel.org,
sudip@vectorindia.org, teddy.wang@siliconmotion.com,
linux-kernel@vger.kernel.org, sudipm.mukherjee@gmail.com
Subject: Re: [PATCH] staging: sm750fb: Fix printk() style warning
Date: Mon, 10 Oct 2016 14:31:46 +0000 [thread overview]
Message-ID: <20161010143146.GA8218@gmail.com> (raw)
In-Reply-To: <20161007091204.GA29629@rapoport-lnx>
On Fri, Oct 07, 2016 at 11:12:04AM +0200, Mike Rapoport wrote:
> On Thu, Oct 06, 2016 at 09:27:36PM -0700, Edward Lipinsky wrote:
> > On Sun, Oct 02, 2016 at 08:13:01PM +0200, Greg KH wrote:
> > > On Sun, Oct 02, 2016 at 11:05:05AM -0700, Edward Lipinsky wrote:
> > > > This patch fixes the checkpatch.pl warning:
> > > >
> > > > WARNING: printk() should include KERN_ facility level
> > > >
> > > > Signed-off-by: Edward Lipinsky <ellipinsky@gmail.com>
> > > > ---
> > > > drivers/staging/sm750fb/ddk750_help.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/staging/sm750fb/ddk750_help.c b/drivers/staging/sm750fb/ddk750_help.c
> > > > index 9637dd3..e72a29c 100644
> > > > --- a/drivers/staging/sm750fb/ddk750_help.c
> > > > +++ b/drivers/staging/sm750fb/ddk750_help.c
> > > > @@ -11,7 +11,7 @@ void ddk750_set_mmio(void __iomem *addr, unsigned short devId, char revId)
> > > > devId750 = devId;
> > > > revId750 = revId;
> > > > if (revId = 0xfe)
> > > > - printk("found sm750le\n");
> > > > + pr_info("found sm750le\n");
> > >
> > > Why can't you use dev_info() here?
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > It should work, but I'm not sure what should change in the header files to
> > do it--esp. to make the dev parameter available in ddk750_help.c. (Only
> > sm750.c uses dev_ style logging now, the rest of the driver still uses pr_*.)
>
> This printk can be moved to lynxfb_pci_probe, and then it should be no
> problem to use dev_info. Just make sure to update the commit message
> appropriately.
>
> > Thanks,
> >
> > Ed Lipinsky
>
> --
> Sincerely yours,
> Mike.
>
Thanks, that makes sense. I tried deleting the if statement and printk()
from ddk750_help.c, and adding the following in lynxfb_pci_probe() after
calling hw_sm750_map() and checking for errors:
if (sm750_dev->revid = 0xfe)
dev_info(&pdev->dev, "found sm750le\n");
The driver compiles, loads and unloads ok with this code.
Does this look correct?
Regards,
Ed L.
WARNING: multiple messages have this Message-ID (diff)
From: Edward Lipinsky <ellipinsky@gmail.com>
To: Mike Rapoport <mike.rapoport@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-fbdev@vger.kernel.org,
sudip@vectorindia.org, teddy.wang@siliconmotion.com,
linux-kernel@vger.kernel.org, sudipm.mukherjee@gmail.com
Subject: Re: [PATCH] staging: sm750fb: Fix printk() style warning
Date: Mon, 10 Oct 2016 07:31:46 -0700 [thread overview]
Message-ID: <20161010143146.GA8218@gmail.com> (raw)
In-Reply-To: <20161007091204.GA29629@rapoport-lnx>
On Fri, Oct 07, 2016 at 11:12:04AM +0200, Mike Rapoport wrote:
> On Thu, Oct 06, 2016 at 09:27:36PM -0700, Edward Lipinsky wrote:
> > On Sun, Oct 02, 2016 at 08:13:01PM +0200, Greg KH wrote:
> > > On Sun, Oct 02, 2016 at 11:05:05AM -0700, Edward Lipinsky wrote:
> > > > This patch fixes the checkpatch.pl warning:
> > > >
> > > > WARNING: printk() should include KERN_ facility level
> > > >
> > > > Signed-off-by: Edward Lipinsky <ellipinsky@gmail.com>
> > > > ---
> > > > drivers/staging/sm750fb/ddk750_help.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/staging/sm750fb/ddk750_help.c b/drivers/staging/sm750fb/ddk750_help.c
> > > > index 9637dd3..e72a29c 100644
> > > > --- a/drivers/staging/sm750fb/ddk750_help.c
> > > > +++ b/drivers/staging/sm750fb/ddk750_help.c
> > > > @@ -11,7 +11,7 @@ void ddk750_set_mmio(void __iomem *addr, unsigned short devId, char revId)
> > > > devId750 = devId;
> > > > revId750 = revId;
> > > > if (revId == 0xfe)
> > > > - printk("found sm750le\n");
> > > > + pr_info("found sm750le\n");
> > >
> > > Why can't you use dev_info() here?
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > It should work, but I'm not sure what should change in the header files to
> > do it--esp. to make the dev parameter available in ddk750_help.c. (Only
> > sm750.c uses dev_ style logging now, the rest of the driver still uses pr_*.)
>
> This printk can be moved to lynxfb_pci_probe, and then it should be no
> problem to use dev_info. Just make sure to update the commit message
> appropriately.
>
> > Thanks,
> >
> > Ed Lipinsky
>
> --
> Sincerely yours,
> Mike.
>
Thanks, that makes sense. I tried deleting the if statement and printk()
from ddk750_help.c, and adding the following in lynxfb_pci_probe() after
calling hw_sm750_map() and checking for errors:
if (sm750_dev->revid == 0xfe)
dev_info(&pdev->dev, "found sm750le\n");
The driver compiles, loads and unloads ok with this code.
Does this look correct?
Regards,
Ed L.
next prev parent reply other threads:[~2016-10-10 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 18:05 [PATCH] staging: sm750fb: Fix printk() style warning Edward Lipinsky
2016-10-02 18:05 ` Edward Lipinsky
2016-10-02 18:13 ` Greg KH
2016-10-02 18:13 ` Greg KH
2016-10-07 4:27 ` Edward Lipinsky
2016-10-07 4:27 ` Edward Lipinsky
2016-10-07 9:12 ` Mike Rapoport
2016-10-07 9:12 ` Mike Rapoport
2016-10-10 14:31 ` Edward Lipinsky [this message]
2016-10-10 14:31 ` Edward Lipinsky
2016-10-13 14:39 ` Mike Rapoport
2016-10-13 14:39 ` Mike Rapoport
2016-10-14 5:18 ` Edward Lipinsky
2016-10-14 5:18 ` Edward Lipinsky
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=20161010143146.GA8218@gmail.com \
--to=ellipinsky@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.rapoport@gmail.com \
--cc=sudip@vectorindia.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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 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.