From: "Martin K. Petersen" <mkp@mkp.net>
To: Michael E Brown <michael_e_brown@dell.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: block ioctl to read/write last sector
Date: 14 Feb 2001 09:23:49 -0500 [thread overview]
Message-ID: <yq13ddh2vii.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0102132348560.1882-100000@carthage.michaels-house.net>
In-Reply-To: <Pine.LNX.4.30.0102132348560.1882-100000@carthage.michaels-house.net>
>>>>> "Michael" == Michael E Brown <michael_e_brown@dell.com> writes:
Michael,
Michael> It looks like the numbers we picked for our respective IOCTLs
Michael> conflict. I think I can change mine to the next higher since
Michael> your patch seems to have been around longer.
If you could pick another number that would be great. All the people
out there using XFS rely on the BLKSETSIZE ioctl, and mkfs.xfs would
break horribly with your patch.
Michael> What is the general way to deal with these conflicts?
Whoever applies the patch to the official tree deals with them :)
--
Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc.
mkp@linuxcare.com, http://www.linuxcare.com/
SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/
next prev parent reply other threads:[~2001-02-14 19:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 22:54 block ioctl to read/write last sector Andries.Brouwer
2001-02-13 19:24 ` Martin K. Petersen
2001-02-14 5:51 ` Michael E Brown
2001-02-14 14:23 ` Martin K. Petersen [this message]
2001-02-13 23:37 ` Michael E Brown
2001-02-14 0:21 ` Manfred Spraul
2001-02-14 5:47 ` Michael E Brown
-- strict thread matches above, loose matches on Subject: below --
2001-02-13 23:49 Andries.Brouwer
2001-02-14 14:19 ` Michael E Brown
2001-02-14 1:00 Matt_Domsch
2001-02-14 12:31 David Balazic
2001-02-14 14:10 ` Michael E Brown
2001-02-17 7:29 ` Andre Hedrick
2001-02-14 13:26 Matt_Domsch
2001-02-14 15:43 Andries.Brouwer
2001-02-14 15:56 ` Michael E Brown
2001-02-14 15:59 ` Michael E Brown
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=yq13ddh2vii.fsf@jaguar.mkp.net \
--to=mkp@mkp.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michael_e_brown@dell.com \
/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