From: Tejun Heo <tj@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] libata-eh: Use switch() instead of sparse array for protocol strings
Date: Mon, 9 Jan 2017 12:31:54 -0500 [thread overview]
Message-ID: <20170109173154.GE12827@mtj.duckdns.org> (raw)
In-Reply-To: <20170109172723.GA30423@infradead.org>
Hello,
On Mon, Jan 09, 2017 at 09:27:23AM -0800, Christoph Hellwig wrote:
> On Mon, Jan 09, 2017 at 05:30:02PM +0100, Geert Uytterhoeven wrote:
> > > ata_force_param_buf is __initdata and shouldn't really matter.
> >
> > It mainly matters because of e.g. bootloader limitations.
>
> Do we need a full 4k for the force parameters? What would a typical
> command line for it look like?
Maybe a couple hundreds bytes at max, but it's a bit weird to restrict
this given that it is bss, not gigantic and __initdata. What kind of
bootloader limitations are we talking about?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-01-09 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 14:49 [PATCH] libata-eh: Use switch() instead of sparse array for protocol strings Geert Uytterhoeven
2017-01-09 15:23 ` Tejun Heo
2017-01-09 15:40 ` Geert Uytterhoeven
2017-01-09 16:04 ` Tejun Heo
2017-01-09 16:21 ` Christoph Hellwig
2017-01-09 17:22 ` Christoph Hellwig
2017-01-09 17:30 ` Tejun Heo
2017-01-09 16:30 ` Geert Uytterhoeven
2017-01-09 17:27 ` Christoph Hellwig
2017-01-09 17:31 ` Tejun Heo [this message]
2017-01-09 18:25 ` Geert Uytterhoeven
2017-01-09 19:41 ` Tejun Heo
2017-01-09 20:28 ` Geert Uytterhoeven
2017-01-09 20:31 ` Tejun Heo
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=20170109173154.GE12827@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox