From: Varka Bhadram <varkabhadram@gmail.com>
To: LIYONG <sdliyong@gmail.com>,
"alex.aring@gmail.com" <alex.aring@gmail.com>,
"linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv1 bluetooth-next] cc2520: set the default fifo pin value from platform data
Date: Mon, 10 Aug 2015 21:08:24 +0530 [thread overview]
Message-ID: <55C8C570.9060102@gmail.com> (raw)
In-Reply-To: <BLU168-W12778BE0A70F0EA756A9E8CD6700@phx.gbl>
Yup... :-) Your name in the From (LIYONG) address is different from SOB (Yong Li) address.
It should be same, please fix your email-client.
On 08/10/2015 12:59 PM, LIYONG wrote:
> In case of the device tree support is disabled, the fifo_pin is uninitialized, this
> patch will set the fifo_pin value based on platform data
>
> Signed-off-by: Yong Li<sdliyong@gmail.com>
> ---
> drivers/net/ieee802154/cc2520.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ieee802154/cc2520.c b/drivers/net/ieee802154/cc2520.c
> index 613dae5..c5b54a1 100644
> --- a/drivers/net/ieee802154/cc2520.c
> +++ b/drivers/net/ieee802154/cc2520.c
> @@ -833,6 +833,7 @@ static int cc2520_get_platform_data(struct spi_device *spi,
> if (!spi_pdata)
> return -ENOENT;
> *pdata = *spi_pdata;
> + priv->fifo_pin = pdata->fifo;
> return 0;
> }
>
> --
> 2.1.0
>
>
This patch is not applying.
Please use 'git format-patch' to generate the patch. And send it by 'git send-email'
In your case:
git commit -am -s "cc2520: set the default fifo pin value from platform data"
git format-patch --subject-prefix="PATCH v2 bluetooth-next" -1
git send-email 0001-....
--
Varka Bhadram.
prev parent reply other threads:[~2015-08-10 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 7:29 [PATCHv1 bluetooth-next] cc2520: set the default fifo pin value from platform data LIYONG
2015-08-10 7:29 ` LIYONG
2015-08-10 15:38 ` Varka Bhadram [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=55C8C570.9060102@gmail.com \
--to=varkabhadram@gmail.com \
--cc=alex.aring@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdliyong@gmail.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.