linux-kernel - Re: [PATCH v2 0/5] Smart Card(SC) interface, TI USIM & NxP SC phy driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140528004147.GA9699@kroah.com>
Date:	Tue, 27 May 2014 17:41:47 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Satish Patel <satish.patel@...com>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
	rob@...dley.net, tony@...mide.com, grant.likely@...aro.org,
	robh+dt@...nel.org
Subject: Re: [PATCH v2 0/5] Smart Card(SC) interface, TI USIM & NxP SC phy
 driver

On Fri, May 16, 2014 at 09:14:34AM +0530, Satish Patel wrote:
> 
> On 1/30/2014 6:35 PM, Greg KH wrote:
> >On Thu, Jan 30, 2014 at 11:22:48AM +0530, Satish Patel wrote:
> >>On 1/20/2014 10:03 AM, Satish Patel wrote:
> >>>Changes from v1:
> >>>* RFC(v1) comments are fixed
> >>>
> >>>** removed "gpio_to_irq" as GPIO controller process  cell from DT and
> >>>give it to DT node
> >>>** comments on documentation
> >>>** few other comments on null checks are resolved
> >>>
> >>>* BWT timing configuration is added to ti-usim driver
> >>>
> >>>v1 cover letter link#
> >>>https://lkml.org/lkml/2014/1/6/250
> >>>
> >>>Satish Patel (5):
> >>>   sc_phy:SmartCard(SC) PHY interface to SC controller
> >>>   misc: tda8026: Add NXP TDA8026 PHY driver
> >>>   char: ti-usim: Add driver for USIM module on AM43xx
> >>>   ARM: dts: AM43xx: DT entries added for ti-usim
> >>>   ARM: dts: AM43xx-epos-evm: DT entries  for ti-usim and phy
> >>>
> >>>  Documentation/devicetree/bindings/misc/tda8026.txt |   19 +
> >>>  .../devicetree/bindings/ti-usim/ti-usim.txt        |   31 +
> >>>  Documentation/sc_phy.txt                           |  171 ++
> >>>  arch/arm/boot/dts/am4372.dtsi                      |   10 +
> >>>  arch/arm/boot/dts/am43x-epos-evm.dts               |   43 +
> >>>  drivers/char/Kconfig                               |    7 +
> >>>  drivers/char/Makefile                              |    1 +
> >>>  drivers/char/ti-usim-hw.h                          |  863 +++++++++
> >>>  drivers/char/ti-usim.c                             | 1859 ++++++++++++++++++++
> >>>  drivers/misc/Kconfig                               |    7 +
> >>>  drivers/misc/Makefile                              |    1 +
> >>>  drivers/misc/tda8026.c                             | 1255 +++++++++++++
> >>>  include/linux/sc_phy.h                             |  132 ++
> >>>  include/linux/ti-usim.h                            |   98 +
> >>>  14 files changed, 4497 insertions(+), 0 deletions(-)
> >>>  create mode 100644 Documentation/devicetree/bindings/misc/tda8026.txt
> >>>  create mode 100644 Documentation/devicetree/bindings/ti-usim/ti-usim.txt
> >>>  create mode 100644 Documentation/sc_phy.txt
> >>>  create mode 100644 drivers/char/ti-usim-hw.h
> >>>  create mode 100644 drivers/char/ti-usim.c
> >>>  create mode 100644 drivers/misc/tda8026.c
> >>>  create mode 100644 include/linux/sc_phy.h
> >>>  create mode 100644 include/linux/ti-usim.h
> >>Any comments on this patch series ?
> >>
> >>If not,
> >>Can you accept these patches for next merge window
> >It's the middle of this merge window, and I can't accept any patches
> >until after 3.14-rc1 is out, at which point I'll start to work on my
> >patch backlog.
> Are these to be consider for next submission ? Or you want me to start
> review cycle one more time.

I don't have them in my queue, so please resend.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/