My Dear Friend,
Let me first of all inform you, I got your email address from a mail Directory
and decided to mail you for a permission to go ahead. I am Mrs. Anna Blair from
United Kingdom, married to Dr. Anthony R. Blair who worked with Texaco Oil
Company in Malaysia before he died in a
Hi!
NeilBrown 于2018年12月4日周二 上午5:55写道：
>
> On Mon, Dec 03 2018, Chuanhong Guo wrote:
>
> > Under MORE_BUF_MODE the controller will always shift one bit out of
> > spi_opcode if (mosi_bit_cnt > 0) && (cmd_bit_cnt == 0) so the full-
> > duplex mode is broken since we can't read anything from MISO
This patch adds RIFFA PCIe linux driver for
https://github.com/promach/riffa/tree/full_duplex/driver/linux
This staging driver is modified from this upstream driver at
https://github.com/KastnerRG/riffa/tree/master/driver/linux
For further details, please refer to
On Tue, Dec 04, 2018 at 02:19:38AM +, Cheng Fei Phung wrote:
> This patch adds RIFFA PCIe linux driver for
> https://github.com/promach/riffa/tree/full_duplex/driver/linux
>
> This staging driver is modified from this upstream driver at
>
On 01.12.18 02:25, Wei Yang wrote:
> On Fri, Nov 30, 2018 at 06:59:19PM +0100, David Hildenbrand wrote:
>> Memory onlining should always be handled by user space, because only user
>> space knows which use cases it wants to satisfy. E.g. memory might be
>> onlined to the MOVABLE zone even if it
The list is still rejecting @microsoft.com patches... :(
I mentioned this last time when you guys were complaining that no one
reads your patches and someone sent me a link to marc.info. I want to
help but obviously no one has time to look at patches on marc.info...
regards,
dan carpenter
This SPI controller seems to be tested on SPI flash only before mass
production and some bits are swizzled under other SPI modes probably
due to incorrect wiring inside the silicon. Reject all modes except
mode0 because they are broken.
Signed-off-by: Chuanhong Guo
---
Under MORE_BUF_MODE the controller will always shift one bit out of
spi_opcode if (mosi_bit_cnt > 0) && (cmd_bit_cnt == 0) so the full-
duplex mode is broken since we can't read anything from MISO during
writing spi_opcode.
This piece of code also make CS1 unavailable since it forces the
broken
Hi Rui,
On Thu, Nov 22, 2018 at 03:18:25PM +, Rui Miguel Silva wrote:
> Adds MIPI CSI-2 subdev for i.MX7 to connect with sensors with a MIPI
> CSI-2 interface.
>
> Signed-off-by: Rui Miguel Silva
> ---
> drivers/staging/media/imx/Makefile |1 +
>
On Sun, 2 Dec 2018 16:10:45 -0200
Marcelo Schmitt wrote:
> On 11/25, Jonathan Cameron wrote:
> > On Thu, 22 Nov 2018 10:53:47 -0200
> > Marcelo Schmitt wrote:
> >
> > > Previously, there was an implicit creation of a kfifo which was replaced
> > > by a call to triggered_buffer_setup, which
On Sun, 2 Dec 2018 14:57:12 -0200
Marcelo Schmitt wrote:
> Add a devicetree documentation for the ad5933 and ad5934 impedance
> converter, network analyzer.
>
> Co-Developed-by: Gabriel Capella
Put this in line below Gabriel's sign off - it makes script
parsing of these easier.
On 01.12.18 02:50, Wei Yang wrote:
> On Fri, Nov 30, 2018 at 06:59:20PM +0100, David Hildenbrand wrote:
>> Let's pass a memory block type instead. Pass "MEMORY_BLOCK_NONE" for device
>> memory and for now "MEMORY_BLOCK_UNSPECIFIED" for anything else. No
>> functional change.
>
> I would suggest
On Fri, Nov 30, 2018 at 5:26 PM Yangtao Li wrote:
>
> We already have the DEFINE_SHOW_ATTRIBUTE.There is no need to define
> such a macro,so remove BINDER_DEBUG_ENTRY.
>
> Signed-off-by: Yangtao Li
Acked-by: Todd Kjos
> ---
> drivers/android/binder.c | 48
On Mon, Dec 03, 2018 at 02:50:19PM +0300, Dan Carpenter wrote:
> The list is still rejecting @microsoft.com patches... :(
>
> I mentioned this last time when you guys were complaining that no one
> reads your patches and someone sent me a link to marc.info. I want to
> help but obviously no one
[...]
>>>
>>> + if (type == MEMORY_BLOCK_NONE)
>>> + return -EINVAL;
>>
>> No one will pass in this value. Can we omit this check for now?
>
>I could move it to patch nr 2 I guess, but as I introduce
>MEMORY_BLOCK_NONE here it made sense to keep it in here.
>
Yes, this make sense to
Fix the incomplete kerneldoc header for struct binder_buffer.
Change-Id: If3ca10cf6d90f605a0c078e4cdce28f02a475877
Signed-off-by: Todd Kjos
---
drivers/android/binder_alloc.h | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git
When dumping out binder transactions via a debug node,
the output is too verbose if a process has many nodes.
Change the output for transaction dumps to only display
nodes with pending async transactions.
Signed-off-by: Todd Kjos
---
drivers/android/binder.c | 3 +++
1 file changed, 3
44d8047f1d87a ("binder: use standard functions to allocate fds")
exposed a pre-existing issue in the binder driver.
fdget() is used in ksys_ioctl() as a performance optimization.
One of the rules associated with fdget() is that ksys_close() must
not be called between the fdget() and the fdput().
Add __acquire()/__release() annnotations to fix warnings
in sparse context checking
There is one case where the warning was due to a lack of
a "default:" case in a switch statement where a lock was
being released in each of the cases, so the default
case was added.
Signed-off-by: Todd Kjos
---
On Mon, Dec 03 2018, Chuanhong Guo wrote:
> Under MORE_BUF_MODE the controller will always shift one bit out of
> spi_opcode if (mosi_bit_cnt > 0) && (cmd_bit_cnt == 0) so the full-
> duplex mode is broken since we can't read anything from MISO during
> writing spi_opcode.
> This piece of code
On Mon, Dec 03, 2018 at 12:24:54PM -0800, Todd Kjos wrote:
> Add __acquire()/__release() annnotations to fix warnings
> in sparse context checking
>
> There is one case where the warning was due to a lack of
> a "default:" case in a switch statement where a lock was
> being released in each of
21 matches
Mail list logo
