Skip to content

fix/: change LTOA to LTO10 #529

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: v2.4.8-windows-support
Choose a base branch
from

Conversation

Magic-Kowel
Copy link

LTOA to LTO10

This pull request includes following changes or fixes.

  • Fix

Description

Change LTOA to LTO10

Type of change

  • Refactoring

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have confirmed my fix is effective or that my feature works

Copy link
Member

@vandelvan vandelvan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Magic-Kowel
Did you test these changes? could you share the output of your tests please?
There was no need to change the variable and constant names but it's ok as long as you keep it consistent across all files.
Look into the comment I left please.
Thanks!

@@ -346,7 +346,7 @@ static struct _timeout_tape timeout_lto9_hh[] = {
{-1, -1}
};

static struct _timeout_tape timeout_ltoA_hh[] = {
static struct _timeout_tape timeout_10_hh[] = {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

specify lto not only 10

@Piloalucard
Copy link
Member

Hello @Magic-Kowel
Is there a specific reason to do this change? For what I can assume it seems to be a decision for maintain the decimal way to name the LTO10 generation instead of adopting the already merged hexadecimal way, but why? Is there any advantage?
Thank you in advance for the response!

DRIVE_LTOA = 0x210A, /* Ultrium Gen A */
DRIVE_LTOA_HH = 0x220A, /* Ultrium Gen A Half-High */
DRIVE_LTO10 = 0x210A, /* Ultrium Gen A */
DRIVE_LTO10_HH = 0x220A, /* Ultrium Gen A Half-High */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gen 10 also in the comment?

TC_MP_LTO8D_CART = 0x88, /* LTO8 Data cartridge */
TC_MP_LTO9D_CART = 0x98, /* LTO9 Data cartridge */
TC_MP_LTO10D_CART = 0xA8, /* LTOA Data cartridge */
TC_MP_LTOP10D_CART = 0xA9, /* LTOPA Data cartridge */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

Copy link
Member

@piste-jp piste-jp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I make a few minor comments. It is really great if you accept the changes.

@@ -87,7 +87,7 @@ struct _timeout_tape{
int timeout; /**< SCSI timeout */
};

/* Base timeout value for LTO */
/* Base timeout value for LTO */
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove a space char. It looks inserted accidentally.

Copy link
Member

@piste-jp piste-jp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants