On Sun, Aug 13, 2017 at 04:39:40PM +0200, Christoph Hellwig wrote:
> On Fri, Aug 11, 2017 at 06:01:42PM +0200, Benjamin Block wrote:
> > When the BSG interface is used with bsg-lib, and the user sends a
> > Bidirectional command - so when he gives an input- and output-buffer
> > (most users of our
t the scsi_request out of the request the driver is supposed
> to provide storage for the sense buffer. The bsg-lib code failed to do so,
> though and will crash anytime it is used.
>
> This patch moves bsg-lib to allocate and setup the bsg_job ahead of time,
> and allocate the sense da
On Fri, Aug 11, 2017 at 06:01:42PM +0200, Benjamin Block wrote:
> When the BSG interface is used with bsg-lib, and the user sends a
> Bidirectional command - so when he gives an input- and output-buffer
> (most users of our interface will likely do that, if they wanna get the
> transport-level resp
and will crash anytime it is used.
>
> This patch moves bsg-lib to allocate and setup the bsg_job ahead of time,
> and allocate the sense data, which is used as reply buffer in bsg.
>
> Reported-by: Steffen Maier
> Signed-off-by: Benjamin Block
> Fixes: 82ed4db499b8 (&quo
is supposed
to provide storage for the sense buffer. The bsg-lib code failed to do so,
though and will crash anytime it is used.
This patch moves bsg-lib to allocate and setup the bsg_job ahead of time,
and allocate the sense data, which is used as reply buffer in bsg.
Reported-by: Steffe
gt; > > all bsg users.
> > >
> >
> > Huh? What additional copy? There is one reply-buffer and that is copied
> > into the user-buffer should it contain valid data. Just like in your
> > patch, neither you, nor me touches any of the copy-code. There is also
>
On Fri, Aug 11, 2017 at 03:49:29PM +0200, Benjamin Block wrote:
> On Fri, Aug 11, 2017 at 11:14:15AM +0200, Christoph Hellwig wrote:
> > But patch 1 still creates an additional copy of the sense data for
> > all bsg users.
> >
>
> Huh? What additional copy? There is o
On Fri, Aug 11, 2017 at 11:14:15AM +0200, Christoph Hellwig wrote:
> But patch 1 still creates an additional copy of the sense data for
> all bsg users.
>
Huh? What additional copy? There is one reply-buffer and that is copied
into the user-buffer should it contain valid data. Just lik
ash anytime it is used.
This patch moves bsg-lib to allocate and setup the bsg_job ahead of time,
and allocate the sense data, which is used as reply buffer in bsg.
Reported-by: Steffen Maier
Signed-off-by: Benjamin Block
Fixes: 82ed4db499b8 ("block: split scsi_request out of struct request"
My point was that we now gurantee that that the sense data is not
a stack pointer an a driver can DMA to it. Now for BSG the sense
data is "just" abused as reply, but the point still stands - we
don't want to pass a possible stack pointer to drivers in a data
buffer because we wa
ponse--->++ Used as _Output_
> | + max_len | | | User doesn't initialize
> | (B)| | BSG Reply | User pr
|
| response--->++ Used as _Output_
| + max_len | || User doesn't initialize
| (B)| | BSG Reply | User provides (optional)
| | | e.g. struct fc_bsg_rep
We can't use an on-stack buffer for the sense data, as drivers will
dma to it. So we should reuse the SCSI init_rq_fn() for the BSG
queues and/or implement the same scheme.
Looks fine,
Reviewed-by: Christoph Hellwig
In contrast to the normal SCSI-lib, the BSG block-queue doesn't make use of
any extra init_rq_fn() to make additional allocations during
request-creation, and the request sense-pointer is not used to transport
SCSI sense data, but is used as backing for the bsg_job->reply pointer;
that in
The BSG implementations use the bsg_job's reply buffer as storage for their
own custom reply structures (e.g.: struct fc_bsg_reply or
struct iscsi_bsg_reply). The size of bsg_job's reply buffer and those of
the implementations is not dependent in any way the compiler can currently
check
of your reply on your expression of Interest I will give
you full details,
on how the business will be executed I am open for negotiation.
Thanks for your anticipated cooperation.
Note you might receive this message in your inbox or spam or junk folder,
depends on your web host or server network
Dear Friend
I am contacting you on a business deal of $9,500,000.00 Million United States
Dollars, ready for transfer into your own personal account and if we make this
claim, we will share it on the ratio of 50% / 50% basis, I would like to assure
you that it be 100% risk free and it will be l
Hello Dear,
How are you doing? I hope you are doing well. I am writing as I have written to
you previously without any response from you. I hope all is well with you.I
will appreciate if you will acknowledge your receipt of this mail.
Thank you and have a good day.
Miss Naya
Please Write Me a
lient send request to read frag A
- frag A has been fragmented into frag B and C. So mds fills the reply
with contents of frag B
- client wants to read next frag C. ceph_choose_frag(frag value of C)
return frag A.
The fix is using previous readdir reply to calculate next readdir frag
when pos
lient send request to read frag A
- frag A has been fragmented into frag B and C. So mds fills the reply
with contents of frag B
- client wants to read next frag C. ceph_choose_frag(frag value of C)
return frag A.
The fix is using previous readdir reply to calculate next readdir frag
when pos
I have been trying to reach you
Hello,
How are you doing? I have been sent to inform you that, We have an
inheritance of a deceased client with your surname. Contact Mr Andrew
Bailey Reply Email To: myinf...@gmail.com with your "Full Names" for
more info. Thanks for your understanding.
Reply ASAP thank you
ine ->verify_authorizer_reply().
+* See get_connect_authorizer().
+*/
+ ret = con->ops->verify_authorizer_reply(con, 0);
+ if (ret < 0) {
+ con->error_msg = "bad aut
.org;
linux-
> ker...@vger.kernel.org; Christoph Hellwig
> Subject: Re: [RESEND][PATCH 07/10][SCSI]mpt2sas: Added Reply Descriptor
> Post Queue (RDPQ) Array support
>
>
> Sreekanth,
>
> > We need to satisfy this condition on those system where 32 bit dma
> > consistent ma
Sreekanth,
> We need to satisfy this condition on those system where 32 bit dma
> consistent mask is not supported and it only supports 64 bit dma
> consistent mask. So on these system we can't set
> pci_set_consistent_dma_mask() to DMA_BIT_MASK(32).
Which systems are you talking about?
It seem
On Thu, Jul 24, 2014 at 1:16 AM, Martin K. Petersen
wrote:
>>>>>> "Sreekanth" == Sreekanth Reddy writes:
>
> Sreekanth,
>
> Sreekanth> 2. As per MPI Spec, each set of 8 reply descriptor post
> Sreekanth> queues must have the same value for the u
person which i can
work with.I will tell you more about me when i get a reply from you.
I am awaiting to hear from you
yours Princess joy J.zengo
the replay. First, the driver
doesn't do anything with the replay second the connection is closed
immediately, hence the packet will be just safely discarded in case it
is received and last the driver won't get stuck if the firmware won't
reply.
Signed-off-by: Alexander Usyskin
claiming that his life is what matters most to them not the money. Can
l work with you to claim it? I am the manager so I know the steps to
take to make it legal without any problem.
I will explain more when I get your reply.
PLEASE REPLY VIA: mycontactss @ yandex.com
Harrison
--
Hello
I wish to know if you are able to handle a business transaction worth
€70 million pounds with me for investment project that will benefit
both of us.
Keep this transaction top secret, to avoid jeopardizing this business
transaction.
As I await your urgent reply philipsmarthholdin
_reply().
+* See get_connect_authorizer().
+*/
+ ret = con->ops->verify_authorizer_reply(con, 0);
+ if (ret < 0) {
+ con->error_msg = "bad authorize reply";
+ return ret;
+
_reply().
+* See get_connect_authorizer().
+*/
+ ret = con->ops->verify_authorizer_reply(con, 0);
+ if (ret < 0) {
+ con->error_msg = "bad authorize reply";
+ return ret;
+
arded in case it
is received and last the driver won't get stuck if the firmware won't
reply.
Cc: #4.10+
Signed-off-by: Alexander Usyskin
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus-fixup.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/d
. After
unsuccessful attempts to locate his relations, I decided to contact
you.
Please, endeavour to reply me on my private email below to enhance
effective communication and details on the above matter.
This is my personal E-mail: (barrmaxwel...@hotmail.com).
Thanks for your prompt response.
Mrs
From: Niu Yawei
ll_migrate() should check reply status before trying to read
reply buffer, checking if request is NULL doesn't make sense.
Signed-off-by: Niu Yawei
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8807
Reviewed-on: https://review.whamcloud.com/23666
Reviewed-by: An
From: Niu Yawei
reply_out_callback() should call ptlrpc_schedule_difficult_reply()
to finalize the rs if it's already not on uncommitted list, otherwise,
the rs and the export held by rs could be leaked:
- target_send_reply() sends a difficult reply before the transaction
committed, the
From: Fan Yong
The 'fld_read_server' uses 'RMF_GENERIC_DATA' to hold the 'FLD_QUERY'
RPC reply that is composed of 'struct lu_seq_range_array'. But there
is not registered swabber function for 'RMF_GENERIC_DATA'. So the RPC
peers need to handle
t defines ->get_authorizer()
+* should also define ->verify_authorizer_reply().
+* See get_connect_authorizer().
+*/
+ ret = con->ops->verify_authorizer_reply(con, 0);
+ if (ret < 0) {
+
_reply().
+* See get_connect_authorizer().
+*/
+ ret = con->ops->verify_authorizer_reply(con, 0);
+ if (ret < 0) {
+ con->error_msg = "bad authorize reply";
+ return ret;
+
_reply().
+* See get_connect_authorizer().
+*/
+ ret = con->ops->verify_authorizer_reply(con, 0);
+ if (ret < 0) {
+ con->error_msg = "bad authorize reply";
+ return ret;
+
_reply().
+* See get_connect_authorizer().
+*/
+ ret = con->ops->verify_authorizer_reply(con, 0);
+ if (ret < 0) {
+ con->error_msg = "bad authorize reply";
+ return ret;
+
On 11/17/2016 07:09 AM, Johannes Thumshirn wrote:
> Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
> helper variables bsg_request and bsg_reply. This will be helpfull when
> transitioning to bsg-lib.
>
> Signed-off-by: Johannes Thumshirn
> Revie
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be helpfull when
transitioning to bsg-lib.
Signed-off-by: Johannes Thumshirn
Reviewed-by: Hannes Reinecke
---
drivers/s390/scsi/zfcp_fc.c | 9 +-
drivers/scs
> HBA_STATUS_ERROR
> > > with my patches and without.
>
> Please ignore my last mails, apparently it's a wise idea to check which user
> id one has before running zfcp_ping...
>
> The good news for this is, I can now recreate the crashes you have and thus
> have a chance
On Tue, Nov 15, 2016 at 03:31:27PM +0100, Steffen Maier wrote:
> Hi Johannes,
>
> On 11/15/2016 12:56 PM, Johannes Thumshirn wrote:
> > On Tue, Oct 25, 2016 at 09:43:14AM +0200, Johannes Thumshirn wrote:
> > > On Fri, Oct 14, 2016 at 09:38:21AM +0200, Johannes Thumshirn wrote:
> > > > On Thu, Oct
On Tue, Nov 15, 2016 at 03:31:27PM +0100, Steffen Maier wrote:
> Hi Johannes,
>
> On 11/15/2016 12:56 PM, Johannes Thumshirn wrote:
> > On Tue, Oct 25, 2016 at 09:43:14AM +0200, Johannes Thumshirn wrote:
> > > On Fri, Oct 14, 2016 at 09:38:21AM +0200, Johannes Thumshirn wrote:
> > > > On Thu, Oct
Hi Johannes,
On 11/15/2016 12:56 PM, Johannes Thumshirn wrote:
On Tue, Oct 25, 2016 at 09:43:14AM +0200, Johannes Thumshirn wrote:
On Fri, Oct 14, 2016 at 09:38:21AM +0200, Johannes Thumshirn wrote:
On Thu, Oct 13, 2016 at 05:55:11PM +0200, Steffen Maier wrote:
Hm, still behaves for me like I
On Tue, Oct 25, 2016 at 09:43:14AM +0200, Johannes Thumshirn wrote:
> On Fri, Oct 14, 2016 at 09:38:21AM +0200, Johannes Thumshirn wrote:
> > On Thu, Oct 13, 2016 at 05:55:11PM +0200, Steffen Maier wrote:
> > > Hm, still behaves for me like I reported for v2:
> > > http://marc.info/?l=linux-scsi&m=
request *bsg_request = job->request;
5d54: e3 10 c0 18 00 04 lg %r1,24(%r12)
struct fc_bsg_reply *bsg_reply = job->reply;
5d5a: e3 b0 c0 20 00 04 lg %r11,32(%r12)
int cmdlen = sizeof(uint32_t); /* start with length of msgcode */
in
On Fri, Oct 14, 2016 at 09:38:21AM +0200, Johannes Thumshirn wrote:
> On Thu, Oct 13, 2016 at 05:55:11PM +0200, Steffen Maier wrote:
> > Hm, still behaves for me like I reported for v2:
> > http://marc.info/?l=linux-scsi&m=147637177902937&w=2
>
> Hi Steffen,
>
> Can you please try the following o
fc_bsg_request_handler(struct request_queue *q,
> > > > struct Scsi_Host *shost,
> > > > /* check if we have the msgcode value at least */
> > > > if (job->request_len < sizeof(uint32_t)) {
> > > >
> On 10/28/2016 01:31 PM, Hannes Reinecke wrote:
> > On 10/28/2016 11:53 AM, Steffen Maier wrote:
> >> On 10/13/2016 06:24 PM, Johannes Thumshirn wrote:
> >>> On Thu, Oct 13, 2016 at 05:15:25PM +0200, Steffen Maier wrote:
...
> fc_bsg_request_handler()
> req->errors = -ENXI
aster
3087864ce3d7282f59021245d8a5f83ef1caef18 is the first bad commit
commit 3087864ce3d7282f59021245d8a5f83ef1caef18
Author: Johannes Thumshirn
Date: Wed Oct 12 15:06:28 2016 +0200
scsi: don't use fc_bsg_job::request and fc_bsg_job::reply directly
Don't use fc_bsg_job::request and fc_bsg_job::reply di
> 3087864ce3d7282f59021245d8a5f83ef1caef18 is the first bad commit
>>>> commit 3087864ce3d7282f59021245d8a5f83ef1caef18
>>>> Author: Johannes Thumshirn
>>>> Date: Wed Oct 12 15:06:28 2016 +0200
>>>>
>>>> scsi: don't use fc_bsg_j
annes Thumshirn
Date: Wed Oct 12 15:06:28 2016 +0200
scsi: don't use fc_bsg_job::request and fc_bsg_job::reply directly
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be helpfull when
trans
On Fri, Oct 14, 2016 at 09:38:21AM +0200, Johannes Thumshirn wrote:
> On Thu, Oct 13, 2016 at 05:55:11PM +0200, Steffen Maier wrote:
> > Hm, still behaves for me like I reported for v2:
> > http://marc.info/?l=linux-scsi&m=147637177902937&w=2
>
> Hi Steffen,
>
> Can you please try the following o
Dear Beneficiary,
I am Julie Leach, 50 years old lucky woman from Three Rivers, Michigan who won
$310.5 Million Dollars Powerball Jackpot on September 30, 2015. I wish to
inform you that your email was randomly selected via Google & Facebook
sponsored email-draws as one of our beneficiaries to
On Thu, Oct 13, 2016 at 05:55:11PM +0200, Steffen Maier wrote:
> Hm, still behaves for me like I reported for v2:
> http://marc.info/?l=linux-scsi&m=147637177902937&w=2
Hi Steffen,
Can you please try the following on top of 2/16?
diff --git a/drivers/scsi/scsi_transport_fc.c b/drivers/scsi/scsi_
Hm, still behaves for me like I reported for v2:
http://marc.info/?l=linux-scsi&m=147637177902937&w=2
On 10/13/2016 05:00 PM, Johannes Thumshirn wrote:
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be h
On Thu, Oct 13, 2016 at 05:55:11PM +0200, Steffen Maier wrote:
> Hm, still behaves for me like I reported for v2:
> http://marc.info/?l=linux-scsi&m=147637177902937&w=2
>
Well given what you've wrote for v2 it's kinda expected.
Byte,
Johannes
--
Johannes Thumshirn
n left to test after this (roughly 1 step)
> [3087864ce3d7282f59021245d8a5f83ef1caef18] scsi: don't use
> fc_bsg_job::request and fc_bsg_job::reply directly
> $ git bisect bad
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [81aea44720d22d2e0c4a2613ae8b1c256ef6b0cb]
steps)
[bef6da201de1bb81bb4d9511f9a155862efc251f] scsi: Unify interfaces of
fc_bsg_jobdone and bsg_job_done
$ git bisect bad
Bisecting: 1 revision left to test after this (roughly 1 step)
[3087864ce3d7282f59021245d8a5f83ef1caef18] scsi: don't use
fc_bsg_job::request and fc_bsg_job::reply directly
$
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be helpfull when
transitioning to bsg-lib.
Signed-off-by: Johannes Thumshirn
Reviewed-by: Hannes Reinecke
---
drivers/s390/scsi/zfcp_fc.c | 9 +-
drivers/scs
On 10/12/2016 03:06 PM, Johannes Thumshirn wrote:
> Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
> helper variables bsg_request and bsg_reply. This will be helpfull when
> transitioning to bsg-lib.
>
> Signed-off-by: Johannes Thumshirn
> -
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be helpfull when
transitioning to bsg-lib.
Signed-off-by: Johannes Thumshirn
---
drivers/s390/scsi/zfcp_fc.c | 9 +-
drivers/scsi/bfa/bfad_bsg.c
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be helpfull when
transitioning to bsg-lib.
Signed-off-by: Johannes Thumshirn
---
drivers/scsi/scsi_transport_fc.c | 37 +++--
1
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be helpfull when
transitioning to bsg-lib.
Signed-off-by: Johannes Thumshirn
---
drivers/scsi/qla2xxx/qla_bsg.c | 264 +++-
dr
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be helpfull when
transitioning to bsg-lib.
Signed-off-by: Johannes Thumshirn
---
drivers/scsi/ibmvscsi/ibmvfc.c | 22 --
1 file changed, 12 inser
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be helpfull when
transitioning to bsg-lib.
Signed-off-by: Johannes Thumshirn
---
drivers/s390/scsi/zfcp_fc.c | 9 ++---
1 file changed, 6 insertions(+), 3 dele
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be helpfull when
transitioning to bsg-lib.
Signed-off-by: Johannes Thumshirn
---
drivers/scsi/bfa/bfad_bsg.c | 40 +++-
1 file ch
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be helpfull when
transitioning to bsg-lib.
Signed-off-by: Johannes Thumshirn
---
drivers/scsi/lpfc/lpfc_bsg.c | 194 +++
1
Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
helper variables bsg_request and bsg_reply. This will be helpfull when
transitioning to bsg-lib.
Signed-off-by: Johannes Thumshirn
---
drivers/scsi/libfc/fc_lport.c | 23 +--
1 file changed, 13 inser
Dear,
My name is Mr Alaine Kamba, I am the Bill and Exchange (assistant)
Manager of Bank of Africa Ouagadougou, Burkina Faso. In my department
I discovered an abandoned sum of eighteen million three hundred
thousand United State of American dollars (18.3MILLION USA DOLLARS)
in an account that belo
When a reply is deemed lost, we send a ping to find out the other end
received all the request data packets we sent. This should be limited to
client calls and we shouldn't do this on service calls.
Signed-off-by: David Howells
---
net/rxrpc/input.c |3 ++-
1 file changed, 2 inser
--
Hi, compliments of the best of moment!
There is a viable business opportunity in our company to supply the raw
materials we use in our production which I've been buying from your
region in my former capacity as purchase officer of our company. I
require partnership of a reliable and trust
In a client call, include the serial number of the last DATA packet of the
reply in the final ACK.
Signed-off-by: David Howells
---
net/rxrpc/recvmsg.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/net/rxrpc/recvmsg.c b/net/rxrpc/recvmsg.c
index a7458c398b9e
Clear the ACK reason, ACK timer and resend timer when entering the client
reply phase when the first DATA packet is received. New ACKs will be
proposed once the data is queued.
The resend timer is no longer relevant and we need to cancel ACKs scheduled
to probe for a lost reply.
Signed-off-by
If we've sent all the request data in a client call but haven't seen any
sign of the reply data yet, schedule an ACK to be sent to the server to
find out if the reply data got lost.
If the server hasn't yet hard-ACK'd the request data, we send a PING ACK to
demand a response
) transferclaim into
your bank account.
Pleaded, do reply for more details on how we are going to proceed if you are
intrested in this grateful oppurtunity.
Thanks
Mr Andrew Musa,
+22679589703.
Dear sir,
I plead indulgence if i have invaded your privacy.
I have an urgent and important business deal to negotiate with you in
connection to my late client Engineer Victor Walmsley.
Please confirm for detail
Regards,
Barrister Tam David
Tel:+228 91942008
From: Vitaly Fertman
A race between unregister_reply & early reply.
When buffers are busy for the early transfer, they cannon be unlinked
by unregister_reply, so the RPC gets into UNREGISTERING state. The
coming reply_in_callback for the early RPC already has unlinked flag
set due to prev
From: Vitaly Fertman
A race between unregister_reply & early reply.
When buffers are busy for the early transfer, they cannon be unlinked
by unregister_reply, so the RPC gets into UNREGISTERING state. The
coming reply_in_callback for the early RPC already has unlinked flag
set due to prev
Dear Friend,
Pardon me for not having the pleasure of knowing your mindset before making you
this offer and it is utterly confidential and genuine by virtue of its nature I
write to solicit your assistance in a funds transfer deal involving £15.2M.This
fund has been stashed out of the excess pr
, upon
receipt of your reply, i will send to you more details about this
business deal.
I will also direct you on how this deal will be done without any
problem; you must understand that this is 100% free from risk.
Therefore my questions are:-
1. Can you handle this project?
2. Can I give you this
READ AND REPLY URGENT.rtf
Description: RTF file
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mykola Lysenko
commit 1f16ee7fa13649f4e55aa48ad31c3eb0722a62d3 upstream.
We should always send reply for UP request in order
to make downstream device clean-up resources appropriately.
Issue
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit cd8140c673d9ba9be3591220e1b2226d9e1e40d3 upstream.
Commit d15f9d694b77 ("libceph: check data_len in ->alloc_msg()")
mistakenly bumped the log level on the "tid %llu unknown,
(!getmsg->msg_routing);
- cpt = lnet_cpt_of_cookie(getmd->md_lh.lh_cookie);
- lnet_res_lock(cpt);
-
- LASSERT(getmd->md_refcount > 0);
-
if (!msg) {
CERROR("%s: Dropping REPLY from %s: can't allocate msg\n",
Hi Sebastian
As you got correctly i was talking about 4.4.1-rt5 and not 4.1 i replied to by
accident.
Am Freitag, 12. Februar 2016, 10:07:59 schrieb Sebastian Andrzej Siewior:
> On 02/12/2016 09:28 AM, Tim Sander wrote:
> > Hi Sebastian
>
> Hi Tim,
>
> > Am Sonntag, 16. August 2015, 15:56:30 s
ed = 1;
diff --git a/drivers/misc/mei/hw.h b/drivers/misc/mei/hw.h
index 459ad596df66..9daf3f9aed25 100644
--- a/drivers/misc/mei/hw.h
+++ b/drivers/misc/mei/hw.h
@@ -53,6 +53,12 @@
#define HBM_MAJOR_VERSION_DC 2
/*
+ * MEI version with immediate reply to enum request support
+ */
3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Mykola Lysenko
commit 1f16ee7fa13649f4e55aa48ad31c3eb0722a62d3 upstream.
We should always send reply for UP request in order
to m
4.2.8-ckt3 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Mykola Lysenko
commit 1f16ee7fa13649f4e55aa48ad31c3eb0722a62d3 upstream.
We should always send reply for UP request in order
to m
day, December 23, 2015 9:51 PM, Yakir Yang wrote:
> >> On Rockchip platform, sometimes driver would failed at reading EDID
> >> message, and it's caused by the AUX reply flag wouldn't received under
> >> the 100*10us wait time.
> > The problem is specific for
y the AUX reply flag wouldn't received under
the 100*10us wait time.
The problem is specific for Rockchip platform.
Also, 1 ms is long time.
The best way is that your hardware engineers find the root cause.
I cannot understand why your engineers cannot find the root cause. :-(
But after expan
t; >>> After test on rockchiop platform, i found sometims driver would failed
> >>> at reading EDID message. After debugging more, i found that it's okay
> >>> to read_a byte from i2c, but it would failed at AUX transcation if we
> >>> try to ready multi-
On Wednesday, December 23, 2015 9:51 PM, Yakir Yang wrote:
>
> On Rockchip platform, sometimes driver would failed at reading EDID
> message, and it's caused by the AUX reply flag wouldn't received under
> the 100*10us wait time.
The problem is specific for Rockchip platfo
On Rockchip platform, sometimes driver would failed at reading EDID
message, and it's caused by the AUX reply flag wouldn't received under
the 100*10us wait time.
But after expand the wait time a little, the AUX reply flag would be
set, so maybe the wait time is a little critical. B
301 - 400 of 645 matches
Mail list logo
