All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Geliang Tang <geliangtang@163.com>,
	"James E.J. Bottomley" <JBottomley@odin.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] scsi: drop unlikely behind BUG_ON()
Date: Sun, 4 Oct 2015 07:33:29 -0700	[thread overview]
Message-ID: <561138B9.6060004@sandisk.com> (raw)
In-Reply-To: <a89c7bef0699c3d3f5e592c58ff3f0a4db482b69.1443937856.git.geliangtang@163.com>

On 10/03/15 23:18, Geliang Tang wrote:
> BUG_ON() already contain an unlikely compiler flag. Drop it.
>
> Signed-off-by: Geliang Tang <geliangtang@163.com>

Reviewed-by: Bart Van Assche <bart.vanassche@sandisk.com>

WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Geliang Tang <geliangtang@163.com>,
	"James E.J. Bottomley" <JBottomley@odin.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] scsi: drop unlikely behind BUG_ON()
Date: Sun, 4 Oct 2015 07:33:29 -0700	[thread overview]
Message-ID: <561138B9.6060004@sandisk.com> (raw)
In-Reply-To: <a89c7bef0699c3d3f5e592c58ff3f0a4db482b69.1443937856.git.geliangtang@163.com>

On 10/03/15 23:18, Geliang Tang wrote:
> BUG_ON() already contain an unlikely compiler flag. Drop it.
>
> Signed-off-by: Geliang Tang <geliangtang@163.com>

Reviewed-by: Bart Van Assche <bart.vanassche@sandisk.com>


  parent reply	other threads:[~2015-10-04 14:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04  6:18 [PATCH 1/3] scsi: drop unlikely behind BUG_ON() Geliang Tang
2015-10-04  6:18 ` [PATCH 2/3] sched/core: " Geliang Tang
2015-10-04  6:18   ` [PATCH 3/3] mm/nommu: " Geliang Tang
2015-10-04  6:18     ` Geliang Tang
2015-10-04 11:02     ` Leon Romanovsky
2015-10-04 11:02       ` Leon Romanovsky
2015-10-05  2:04       ` Davidlohr Bueso
2015-10-05  2:04         ` Davidlohr Bueso
2015-10-05  7:49         ` Leon Romanovsky
2015-10-05  7:49           ` Leon Romanovsky
2015-10-05  1:50     ` Davidlohr Bueso
2015-10-05  1:50       ` Davidlohr Bueso
2015-10-05  2:30       ` Geliang Tang
2015-10-05  2:30         ` Geliang Tang
2015-10-05  3:37         ` Davidlohr Bueso
2015-10-05  3:37           ` Davidlohr Bueso
2015-10-04 14:33 ` Bart Van Assche [this message]
2015-10-04 14:33   ` [PATCH 1/3] scsi: " Bart Van Assche

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=561138B9.6060004@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=JBottomley@odin.com \
    --cc=geliangtang@163.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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.