From: Justin Capella <justincapella@gmail.com>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Kalle Valo <kvalo@codeaurora.org>,
LKML <linux-kernel@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] ath10k: Use device_get_match_data() to simplify code
Date: Sat, 25 Jan 2020 20:18:40 -0800 [thread overview]
Message-ID: <CAMrEMU-e55q7uvd220+1kuYJ4Xa-4ckz5CvYezCj2ahn_K8t9w@mail.gmail.com> (raw)
In-Reply-To: <20200123232944.39247-1-swboyd@chromium.org>
Maybe use dev here as well?
> dev_err(&pdev->dev, "failed to find matching device tree id\n");
WARNING: multiple messages have this Message-ID (diff)
From: Justin Capella <justincapella@gmail.com>
To: Stephen Boyd <swboyd@chromium.org>
Cc: netdev@vger.kernel.org, ath10k <ath10k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [PATCH] ath10k: Use device_get_match_data() to simplify code
Date: Sat, 25 Jan 2020 20:18:40 -0800 [thread overview]
Message-ID: <CAMrEMU-e55q7uvd220+1kuYJ4Xa-4ckz5CvYezCj2ahn_K8t9w@mail.gmail.com> (raw)
In-Reply-To: <20200123232944.39247-1-swboyd@chromium.org>
Maybe use dev here as well?
> dev_err(&pdev->dev, "failed to find matching device tree id\n");
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2020-01-26 4:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 23:29 [PATCH] ath10k: Use device_get_match_data() to simplify code Stephen Boyd
2020-01-23 23:29 ` Stephen Boyd
2020-01-26 4:18 ` Justin Capella [this message]
2020-01-26 4:18 ` Justin Capella
2020-01-26 14:25 ` Kalle Valo
2020-01-26 14:25 ` Kalle Valo
2020-01-26 14:34 ` Kalle Valo
2020-01-26 14:34 ` Kalle Valo
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=CAMrEMU-e55q7uvd220+1kuYJ4Xa-4ckz5CvYezCj2ahn_K8t9w@mail.gmail.com \
--to=justincapella@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=swboyd@chromium.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 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.