From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 219072] After updating to kernel 6.10.0, one of my Western Digital HDD stopped working
Date: Mon, 22 Jul 2024 13:39:14 +0000 [thread overview]
Message-ID: <bug-219072-13602-yfCg9scXYC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219072-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219072
--- Comment #5 from xcreativ@gmail.com ---
Thank you for your quick and prompt response! I'll try and send you an answer
to help you with your work. Could you please suggest how best to do this? Now I
can generate a kernel from packages of an already assembled kernel that my
distribution sends. I do this using mkinitcpio.
To check I need:
1 download kernel sources from git
2 make them
3 tell mkinitcpio where the assembled kernel is located
Right? If yes, in this sequence I need to understand how to correctly download
the kernel with the specified commit.
Which command git.
As I understand it, this is not even the entire kernel, but a patch of the ext4
module.
The fact that you quickly identified the problem and took action on it gave me
a positive bug reporting experience. I understand that I was able to help you
and other users.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-07-22 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-219072-13602@https.bugzilla.kernel.org/>
2024-07-21 21:01 ` [Bug 219072] After updating to kernel 6.10.0, one of my Western Digital HDD stopped working bugzilla-daemon
2024-07-21 21:02 ` bugzilla-daemon
2024-07-21 21:05 ` bugzilla-daemon
2024-07-22 10:33 ` bugzilla-daemon
2024-07-22 13:39 ` bugzilla-daemon [this message]
2024-07-22 19:03 ` bugzilla-daemon
2024-07-22 20:31 ` bugzilla-daemon
2024-07-22 21:39 ` bugzilla-daemon
2024-07-24 10:51 ` bugzilla-daemon
2024-07-25 1:14 ` bugzilla-daemon
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=bug-219072-13602-yfCg9scXYC@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@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 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.