Linux USB
 help / color / mirror / Atom feed
From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: [PATCH v1 1/2] usb: dwc3: core: add support for remapping global register start address
Date: Tue, 11 Apr 2023 03:11:19 +0000	[thread overview]
Message-ID: <e82cf3f4d6bc4862bdb68b3c38775719@realtek.com> (raw)
In-Reply-To: <20230411012721.b63dx3oodojby6lf@synopsys.com>

> > > > +     if (dev) {
> > >
> > > Why do we need this if (dev) check? When would this not be the case?
> >
> > I want the variable "fixed_dwc3_globals_regs_start" to be a local variable.
> > So I added an if statement.
> > I can modify it to "if (dev->of_node)" which looks more make sense.
> 
> Why? If it's within this function, it's a local variable. Don't create arbitrary
> condition just to limit the scope of the variable.
> 
> Thanks,
> Thinh
> 

I agree that don't create arbitrary conditions just to limit the scope of variables.
The property "snps,global-regs-starting-offset" is in the device tree,
so checking dev->of_node exists is a must.

Thanks,
Stanley

      reply	other threads:[~2023-04-11  3:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07  6:07 [PATCH v1 1/2] usb: dwc3: core: add support for remapping global register start address Stanley Chang
2023-04-07  6:07 ` [PATCH v1 2/2] dt-bindings: usb: snps,dwc3: Add 'snps,fixed_dwc3_globals_regs_start' quirk Stanley Chang
2023-04-08  2:51   ` Thinh Nguyen
2023-04-10  3:59     ` Stanley Chang[昌育德]
2023-04-08  2:08 ` [PATCH v1 1/2] usb: dwc3: core: add support for remapping global register start address Thinh Nguyen
2023-04-10  4:09   ` Stanley Chang[昌育德]
2023-04-11  1:27     ` Thinh Nguyen
2023-04-11  3:11       ` Stanley Chang[昌育德] [this message]

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=e82cf3f4d6bc4862bdb68b3c38775719@realtek.com \
    --to=stanley_chang@realtek.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox