All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Colin King <colin.king@canonical.com>,
	Richard Weinberger <richard@nod.at>,
	David Woodhouse <dwmw2@infradead.org>,
	Marek Vasut <marek.vasut@gmail.com>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
	linux-mtd@lists.infradead.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: make nand_ooblayout_lp_hamming_ops static
Date: Thu, 11 May 2017 18:35:52 +0000	[thread overview]
Message-ID: <20170511183552.GI70297@google.com> (raw)
In-Reply-To: <20170504160813.23bad4f9@bbrezillon>

On Thu, May 04, 2017 at 04:08:13PM +0200, Boris Brezillon wrote:
> On Thu,  4 May 2017 13:11:00 +0100
> Colin King <colin.king@canonical.com> wrote:
> 
> > From: Colin Ian King <colin.king@canonical.com>
> > 
> > nand_ooblayout_lp_hamming_ops can be made static as it does not need to be
> > in global scope.
> > 
> > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> 
> Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> 
> Brian, feel free to apply this patch directly if you want, otherwise,
> I'll queue it for 4.13.

Eh, queue it for 4.13, or in a fixes branch if you want.

WARNING: multiple messages have this Message-ID (diff)
From: Brian Norris <computersforpeace@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Colin King <colin.king@canonical.com>,
	Richard Weinberger <richard@nod.at>,
	David Woodhouse <dwmw2@infradead.org>,
	Marek Vasut <marek.vasut@gmail.com>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
	linux-mtd@lists.infradead.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: make nand_ooblayout_lp_hamming_ops static
Date: Thu, 11 May 2017 11:35:52 -0700	[thread overview]
Message-ID: <20170511183552.GI70297@google.com> (raw)
In-Reply-To: <20170504160813.23bad4f9@bbrezillon>

On Thu, May 04, 2017 at 04:08:13PM +0200, Boris Brezillon wrote:
> On Thu,  4 May 2017 13:11:00 +0100
> Colin King <colin.king@canonical.com> wrote:
> 
> > From: Colin Ian King <colin.king@canonical.com>
> > 
> > nand_ooblayout_lp_hamming_ops can be made static as it does not need to be
> > in global scope.
> > 
> > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> 
> Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> 
> Brian, feel free to apply this patch directly if you want, otherwise,
> I'll queue it for 4.13.

Eh, queue it for 4.13, or in a fixes branch if you want.

  reply	other threads:[~2017-05-11 18:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 12:11 [PATCH] mtd: nand: make nand_ooblayout_lp_hamming_ops static Colin King
2017-05-04 12:11 ` Colin King
2017-05-04 14:08 ` Boris Brezillon
2017-05-04 14:08   ` Boris Brezillon
2017-05-11 18:35   ` Brian Norris [this message]
2017-05-11 18:35     ` Brian Norris
2017-05-15 20:45 ` Boris Brezillon
2017-05-15 20:45   ` Boris Brezillon

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=20170511183552.GI70297@google.com \
    --to=computersforpeace@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=colin.king@canonical.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=dwmw2@infradead.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=richard@nod.at \
    /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.