From: Tony Camuso <tcamuso@redhat.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Cc: "Schoeller, Patrick (Linux - Houston, TX)" <Patrick.Schoeller@hp.com>
Subject: bfsort whitelist patch apparently applied twice
Date: Mon, 07 Jul 2008 10:35:02 -0400 [thread overview]
Message-ID: <48722996.4050601@redhat.com> (raw)
In the most recent pull from Linus' tree, I see that the patch
I submitted on 14-May-2008 was merged twice in the git log.
commits: a16b4bcd31a73a81b6d2b8ffa6b5f6ed01cf6d64
and: a1676072558854b95336c8f7db76b0504e909a0a
The result is that now the DL360 and DL380 are whitelisted twice
and the DL385 G2 and DL585 G2 are not whitelisted at all!
Can one of these redundant commits be backed out?
Thanks and regards,
Tony
next reply other threads:[~2008-07-07 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 14:35 Tony Camuso [this message]
2008-07-07 16:59 ` bfsort whitelist patch apparently applied twice Jesse Barnes
2008-07-07 18:09 ` Tony Camuso
2008-07-07 22:36 ` Jesse Barnes
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=48722996.4050601@redhat.com \
--to=tcamuso@redhat.com \
--cc=Patrick.Schoeller@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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