The patch titled mac68k: macii adb comment correction has been added to the -mm tree. Its filename is mac68k-macii-adb-comment-correction.patch *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: mac68k: macii adb comment correction From: Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx> Corrects a mistake I made in a comment. Signed-off-by: Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx> Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> Cc: Roman Zippel <zippel@xxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/macintosh/via-macii.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/macintosh/via-macii.c~mac68k-macii-adb-comment-correction drivers/macintosh/via-macii.c --- a/drivers/macintosh/via-macii.c~mac68k-macii-adb-comment-correction +++ a/drivers/macintosh/via-macii.c @@ -111,7 +111,7 @@ static enum macii_state { static struct adb_request *current_req; /* first request struct in the queue */ static struct adb_request *last_req; /* last request struct in the queue */ static unsigned char reply_buf[16]; /* storage for autopolled replies */ -static unsigned char *reply_ptr; /* next byte in req->data or reply_buf */ +static unsigned char *reply_ptr; /* next byte in reply_buf or req->reply */ static int reading_reply; /* store reply in reply_buf else req->reply */ static int data_index; /* index of the next byte to send from req->data */ static int reply_len; /* number of bytes received in reply_buf or req->reply */ _ Patches currently in -mm which might be from fthain@xxxxxxxxxxxxxxxxxxx are mac68k-mailing-list-addresss.patch mac68k-macii-adb-comment-correction.patch mac68k-remove-dead-code.patch mac68k-add-nubus-card-definitions-and-a-typo-fix.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html