From: Alexander Sabourenkov <screwdriver@lxnt.info>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: jeff@garzik.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 2.6.24-rc1] sata_promise: ASIC PRD table bug workaround
Date: Tue, 30 Oct 2007 12:22:16 +0300 [thread overview]
Message-ID: <4726F7C8.3010901@lxnt.info> (raw)
In-Reply-To: <200710300907.l9U97eW8024996@harpo.it.uu.se>
Mikael Pettersson wrote:
>
> Unfortunately the name pdc_qc_prep() is already taken
> [it switches on qc->tf.protocol], so that leaves either pdc_fill_sg()
> [slightly imprecise as you noted], or uglies like __pdc_qc_prep(),
> pdc_qc_prep2(), or pdc_qc_prep_and_fill_sg() as names for the new
> procedure. I welcome suggestions for a better name.
>
pdc_qc_prep_backend() ?
ps:
I almost stuck on naming the function while writing the patch,
put there first that came to mind just to not delay testing.
--
./lxnt
next prev parent reply other threads:[~2007-10-30 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 9:07 [PATCH 2.6.24-rc1] sata_promise: ASIC PRD table bug workaround Mikael Pettersson
2007-10-30 9:22 ` Alexander Sabourenkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-29 15:50 Mikael Pettersson
2007-10-29 19:07 ` Jeff Garzik
2007-10-30 6:09 ` Alexander Sabourenkov
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=4726F7C8.3010901@lxnt.info \
--to=screwdriver@lxnt.info \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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;
as well as URLs for NNTP newsgroup(s).