From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH v1] ath10k: Switch to use new generic UUID API
Date: Wed, 02 Aug 2017 18:19:34 +0300 [thread overview]
Message-ID: <1501687174.29303.357.camel@linux.intel.com> (raw)
In-Reply-To: <87d18erpuv.fsf@kamboji.qca.qualcomm.com>
On Wed, 2017-08-02 at 14:44 +0000, Kalle Valo wrote:
> Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
>
> > There are new types and helpers that are supposed to be used in new
> > code.
> >
> > As a preparation to get rid of legacy types and API functions do
> > the conversion here.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> To which tree are you planning to submit this? Can I take this to my
> ath.git tree?
I guess it's precisely for your tree.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH v1] ath10k: Switch to use new generic UUID API
Date: Wed, 02 Aug 2017 18:19:34 +0300 [thread overview]
Message-ID: <1501687174.29303.357.camel@linux.intel.com> (raw)
In-Reply-To: <87d18erpuv.fsf@kamboji.qca.qualcomm.com>
On Wed, 2017-08-02 at 14:44 +0000, Kalle Valo wrote:
> Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
>
> > There are new types and helpers that are supposed to be used in new
> > code.
> >
> > As a preparation to get rid of legacy types and API functions do
> > the conversion here.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> To which tree are you planning to submit this? Can I take this to my
> ath.git tree?
I guess it's precisely for your tree.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-08-02 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 13:57 [PATCH v1] ath10k: Switch to use new generic UUID API Andy Shevchenko
2017-08-02 13:57 ` Andy Shevchenko
2017-08-02 14:44 ` Kalle Valo
2017-08-02 14:44 ` Kalle Valo
2017-08-02 15:19 ` Andy Shevchenko [this message]
2017-08-02 15:19 ` Andy Shevchenko
2017-08-08 11:07 ` [v1] " Kalle Valo
2017-08-08 11:07 ` 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=1501687174.29303.357.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@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 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.