From: Roberto Fichera <kernel@tekno-soft.it>
To: Fabio Estevam <festevam@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: /sys/fsl_otp patch for linux-fslc v4.4 kernel, where?
Date: Wed, 17 Feb 2016 16:53:31 +0100 [thread overview]
Message-ID: <56C4977B.9060803@tekno-soft.it> (raw)
In-Reply-To: <CAOMZO5AgdcTYgB9YASNYjfiOM4FQaubx8NRvbR5De8Q5T3Ydxg@mail.gmail.com>
On 02/17/2016 04:50 PM, Fabio Estevam wrote:
> On Wed, Feb 17, 2016 at 1:46 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> On Wed, Feb 17, 2016 at 1:43 PM, Roberto Fichera <kernel@tekno-soft.it> wrote:
>>
>>> I've solved the problem by porting the patch for v3.14.x to current kernel-fslc v4.4
>> Nice! What about sending your patch for review?
>>
>> ./scripts/checkpatch.pl -f drivers/nvmem/imx-ocotp.c would point you
>> to the correct folks to submit the patch to.
> Sorry, I meant
> ./scripts/get_maintainer.pl -f drivers/nvmem/imx-ocotp.c
>
My current patch isn't based on drivers/nvmem/imx-ocotp.c
$ lsdiff 0110-fsl_otp-sysfs.patch
a/arch/arm/boot/dts/imx6qdl.dtsi
a/drivers/char/Kconfig
a/drivers/char/Makefile
b/drivers/char/fsl_otp.c
b/include/linux/fsl_otp.h
next prev parent reply other threads:[~2016-02-17 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 16:22 /sys/fsl_otp patch for linux-fslc v4.4 kernel, where? Roberto Fichera
2016-02-17 12:05 ` Fabio Estevam
2016-02-17 13:52 ` Roberto Fichera
2016-02-17 14:14 ` Fabio Estevam
2016-02-17 14:22 ` Roberto Fichera
2016-02-17 15:43 ` Roberto Fichera
2016-02-17 15:46 ` Fabio Estevam
2016-02-17 15:50 ` Fabio Estevam
2016-02-17 15:53 ` Roberto Fichera [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-04 11:25 Colin Wernham
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=56C4977B.9060803@tekno-soft.it \
--to=kernel@tekno-soft.it \
--cc=festevam@gmail.com \
--cc=meta-freescale@yoctoproject.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.