From: Felipe Balbi <balbi@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [v3,1/2] usb: dwc3: pci: Supply device properties via driver data
Date: Thu, 26 Jul 2018 14:50:57 +0300 [thread overview]
Message-ID: <871sbq1ahq.fsf@linux.intel.com> (raw)
Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
> For now all PCI enumerated dwc3 devices require some properties
> to be present. This allows us to unconditionally append them and supply
> via driver_data.
>
> No functional change intended.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
both applied, but I removed your macro below since that only adds
obfuscation and breaks the simple use-case of navigating with the help
of ctags/etags.
next reply other threads:[~2018-07-26 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 11:50 Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-26 12:00 [v3,1/2] usb: dwc3: pci: Supply device properties via driver data Andy Shevchenko
2018-07-26 11:48 Andy Shevchenko
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=871sbq1ahq.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).